GithubHelp home page GithubHelp logo

git-reference's Introduction

Build status

Git - fast, scalable, distributed revision control system

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals.

Git is an Open Source project covered by the GNU General Public License version 2 (some parts of it are under different licenses, compatible with the GPLv2). It was originally written by Linus Torvalds with help of a group of hackers around the net.

Please read the file INSTALL for installation instructions.

Many Git online resources are accessible from https://git-scm.com/ including full documentation and Git related tools.

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.txt for a useful minimum set of commands, and Documentation/git-<commandname>.txt for documentation of each command. If git has been correctly installed, then the tutorial can also be read with man gittutorial or git help tutorial, and the documentation of each command with man git-<commandname> or git help <commandname>.

CVS users may also want to read Documentation/gitcvs-migration.txt (man gitcvs-migration or git help cvs-migration if git is installed).

The user discussion and development of Git take place on the Git mailing list -- everyone is welcome to post bug reports, feature requests, comments and patches to [email protected] (read Documentation/SubmittingPatches for instructions on patch submission and Documentation/CodingGuidelines).

Those wishing to help with error message, usage and informational message string translations (localization l10) should see po/README.md (a po file is a Portable Object file that holds the translations).

To subscribe to the list, send an email to [email protected] (see https://subspace.kernel.org/subscribing.html for details). The mailing list archives are available at https://lore.kernel.org/git/, https://marc.info/?l=git and other archival sites.

Issues which are security relevant should be disclosed privately to the Git Security mailing list [email protected].

The maintainer frequently sends the "What's cooking" reports that list the current status of various development topics to the mailing list. The discussion following them give a good reference for project status, development direction and remaining tasks.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (depending on your mood):

  • random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronunciation of "get" may or may not be relevant.
  • stupid. contemptible and despicable. simple. Take your pick from the dictionary of slang.
  • "global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room.
  • "goddamn idiotic truckload of sh*t": when it breaks

git-reference's People

Contributors

alefteris avatar brntbeer avatar bry4n avatar computerdruid avatar cyjake avatar dstine avatar freshtonic avatar gergelypolonkai avatar hbpasti avatar hectorsector avatar jeffreyguenther avatar jstemmer avatar korrocive avatar leaofelipe avatar longsays avatar mcastner avatar mhenke avatar mikelehen avatar niels-bom-md avatar nilhcem avatar nuysoft avatar nvl avatar pkufranky avatar randomecho avatar rinatio avatar robertd avatar rosetree avatar schacon avatar shawnajean avatar yaotti avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

git-reference's Issues

please tell...

please tell us how to setup git https auth for client. tired googleing....

Translating Git

Hi, is there any chance to translate Git-scm and Git itself to different languages? Thanks!

add "git config remote.origin.pushurl" info

Many times, you clone a repo using

git clone git://github.com/certik/jsplot.git

and you'd like to push in using:

git push origin master

you can do that by:

git config remote.origin.pushurl [email protected]:certik/jsplot.git

it'd be cool to have this trick in the remotes section

issues for git/git repo

In fact, I want to file an issue for the git repository, but in github, I can't file an issue for git (is there no problem with git? lol~~), the problem is: when a project is updated too fast, that is, there are many versions , then the git warehouse will also become very large. This problem is expected to have some trouble for the kernel developers. After all, the first time the warehouse is pulled down, more than one G data will be downloaded. This problem is estimated to be difficult to solve. Of course, most projects will not have this problem, because their version changes will not be so fast, except for kernel and kubernetes, I just want to talk about this problem, that's all

Possible Spelling Error

On the page: http://gitref.org/remotes/

First line of the heading: git remote, reads "Unline centralized version control systems that have..." Maybe 'unline' should be 'unlike'?

Thank you so much for posting this tutorial. It was extremely useful for me getting "ramped up" on using GIT

Make the left navigation bar stay in view

I think that it would be nice to have the left menu visible all the time because one usually skips from one link to another (reads more of them) and for that you have to jump back to the beginning of the page. There is enough unused horizontal space for that.

Take it just as an idea. Otherwise, I like the page and it is helpful even in its current form.
Thank you,
Jan

Feature request: reference cards

I've been giving out git reference cards and wanted a sort of online version of that.

Would you by any chance happen to have a link to such printable cards?

Missing Favicon

Please add favicon to the site. It just gets lost in the tabs of my browser.

git reset HEAD doesn't undo the last commit

The docs for git reset say:
'git reset HEAD undo the last commit and unstage the files'

git reset HEAD will unstage files, but it will not undo the last commit unless you reset HEAD to HEAD~1 or HEAD^.

the sections for git reset --soft and git reset --hard also say the last commit will be undone.

I think this needs to be clarified. Thanks

rebase not mentioned

As a lot of users do switch from svn and need to keep working with svn. Helping them to do it with the git client seems useful.

If this is a wrong statement from a git newbie, I am happy to be told so.

How can I clone this docs and put them in my site?

  1. I saw the index.html have a layout: reference
  2. the _layouts/reference.html have {{ content }}, I think the content such as index.html should be put in this block

But I don't know how can I use it ? Just put the _layouts/reference.html to index.html by hand?

And all the static files such as css/js ... all use absolute path. And I think it should be relative path if the directory is sub directory

GitRef.org site not responding

$ curl -v gitref.org
* Adding handle: conn: 0x7fb803004000
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x7fb803004000) send_pipe: 1, recv_pipe: 0
* Could not resolve host: gitref.org
* Closing connection 0
curl: (6) Could not resolve host: gitref.org

and nslookup:

$ nslookup
> gitref.org
;; Got SERVFAIL reply from 10.0.119.1, trying next server
Server:     10.0.119.1
Address:    10.0.119.1#53

** server can't find gitref.org: NXDOMAIN

Git Bash Command Line Drag & Drop Option

Hello. I used to drag and drop folders to Git Bash command line to change the working directory or to create new repos, but this option is no longer available. I'm using Windows 10 64bit - Any clues about this issue? Thank you.

Typo on front page

The last sentence of the first paragraph should say "present" instead of "preset"...

"The commands are organized into sections of the type of operation you may be trying to do, and will preset the common options and commands needed to accomplish these common tasks."

"git diff" instructions are quite confusing

If you go forward the tutorial and get to http://gitref.org/basic/ following all the previous steps you will get different results in comparation with the tutorial.

I think that you need to run at least once "git commit" to be able to use these command "git diff HEAD" and "git diff --cached"

See you, thanks.

Missing documents for `git subtree`

Current situation:
git subtree --help open up local documents currectly.
While https://git-scm.com/docs/git-subtree is redirected to https://git-scm.com/docs

Expected:
Amend git subtree's online document.

Description of 'git stash apply/pop' should say a merge happens

The description of git stash apply and git stash pop should mention that the stashed changes are merged into the working tree and can result in merge conflicts. It should advise the user how to avoid merge conflicts (by bringing the working tree back to a state where the stash entry applies without conflicts).

git reset --hard description vague

First of all: I could very well be mistaken.

In the git reset --hard section:

The third option is to go --hard and make your working directory look like the index, unstage files and undo any changes made since the last commit. This is the most dangerous option and not working directory safe. Any changes not in the index or have not been commited will be lost.

As the example after this piece of text shows even changes in the index are lost after a git reset --hard. So this text does not seem to be correct.

git stash doesn't stash away unversioned files

You should mention that git stash doesn't stash away files that are not in the index yet. It can cause much trouble if you e.g. do a git clean -dfx on the super-urgent-bugfix branch. However, 1.7.7 and up has git stash -u to do this.

git remote typo

First sentence:

"Unline centralized version control systems that have a client that is very different from a server ..."

should read "Unlike centralized version control ...", I think.

Confusion about git-mv

Hi.
In the section http://gitref.org/basic/#rm-mv you are saying that git-rm is equivalent to three commands:
git rm orig
mv orig new
git add new

Although you emphasize it clearly that git rm removes files from disk, the above example doesn't conform to that. After executing git rm orig, the orig file will be removed from disk, so there will be nothing to apply the mv command to. This may lead to some confusion for novice git users. You should probably add --cached option, like this:
git rm --cached orig
mv orig new
git add new

J

Ndovrorrir

Public git changelog

I'm looking for a list of major changes made to git over the years but I can't find any. Even the main repo doesn't seem to have a changelog file or a wiki to refer this. The main reason is that I want to know what major changes have been made since the release of Pro Git book (which is now 4 years old).

Subsection Anchors

The other day, I tired linking git log -S, but I couldn't. I had to link git log. May I add subsection anchors?

h4-anchor

<h4>
  git log -S
  <small>filter by introduced diff</small>
  <a name="log-s"></a>
</h4>

Thoughts? Thanks!

'rm' and 'mv' description is mixed

'rm' and 'mv' are described in the same section (http://gitref.org/basic/#rm-mv).
In the beginning, 'rm' is explained. Then 'mv'.
And after these, there is this sentence:"In its normal form the command is used to delete files. But it's often easier to just remove the files off your disk and then run git commit -a, which will also automatically remove them from your index.
"

Which gets back to describing 'rm', without mentioning it.
It's quite confusing...

And after it, the 'In a nutshell' section mentions only 'rm', and ignores 'mv'.

git merge No conflict reported!!

local branch:
`
static int __clk_core_init(struct clk_core *core)
{
int ret;
struct clk_core *parent;
unsigned long rate;
int phase;

if (!core)
    return -EINVAL;

clk_prepare_lock();
core->hw->core = core;

ret = clk_pm_runtime_get(core);
if (ret)
    goto unlock;

...
}
`

after branch:
`
static int __clk_core_init(struct clk_core *core)
{
int ret;
struct clk_core *parent;
unsigned long rate;
int phase;

if (!core)
    return -EINVAL;

clk_prepare_lock();

/*
 * Set hw->core after grabbing the prepare_lock to synchronize with
 * callers of clk_core_fill_parent_index() where we treat hw->core
 * being NULL as the clk not being registered yet. This is crucial so
 * that clks aren't parented until their parent is fully registered.
 */
core->hw->core = core;

ret = clk_pm_runtime_get(core);
if (ret)
    goto unlock;

...
}
`

local branch:execute "git merge after"
`
static int __clk_core_init(struct clk_core *core)
{
int ret;
struct clk_core *parent;
unsigned long rate;
int phase;

if (!core)
    return -EINVAL;

clk_prepare_lock();
core->hw->core = core;

/*
 * Set hw->core after grabbing the prepare_lock to synchronize with
 * callers of clk_core_fill_parent_index() where we treat hw->core
 * being NULL as the clk not being registered yet. This is crucial so
 * that clks aren't parented until their parent is fully registered.
 */
core->hw->core = core;

ret = clk_pm_runtime_get(core);
if (ret)
    goto unlock;

...
}
`

Result In two occurrences after merge:"core->hw->core = core;", And it happens every time.

  1. Can this problem be fixed
  2. How can I modify the source code so that this does not happen

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.