Re: Making git disappear when talking about my code

Daniel Barkalow [off-list ref] writes:

Linus has stated a preference on the lkml for being told about branches in 
the syntax used for anonymous pulls: URL branchname.

That is, you say:

  Please pull from:
    git://server/path branch

And he cuts and pastes into the command line:

  git pull git://server/path branch

Now, this syntax isn't available for git-clone, because git-clone puts the 
optional directory to create after the URL. But, in an ideal world, this 
is how it would work; you could see a pull request, and just type "git 
some-command <paste>".

I think I already suggested this to Carl once, but if you 
forget about 'git clone' in this case (or any other cases), your
example would just work.

	$ git init
        $ git pull git://server/path branch

On Wed, 25 Apr 2007, Junio C Hamano wrote:

I think I already suggested this to Carl once, but if you 
forget about 'git clone' in this case (or any other cases), your
example would just work.

   $ git init
   $ git pull git://server/path branch

The problem with this is that it doesn't set up tracking, so while it 
*works*, you are now forever doomed to re-do that

	git pull git://server/path branch

to update, and if you then ever give the wrong branch name you'll try to 
merge and get really confused as a beginner.

		Linus

On Wed, 25 Apr 2007, Junio C Hamano wrote:

I think I already suggested this to Carl once, but if you 
forget about 'git clone' in this case (or any other cases), your
example would just work.

	$ git init
        $ git pull git://server/path branch

Ah, goodie!


Nicolas

On Wed, 25 Apr 2007, Junio C Hamano wrote:

Daniel Barkalow [off-list ref] writes:

quoted

Linus has stated a preference on the lkml for being told about branches in 
the syntax used for anonymous pulls: URL branchname.

That is, you say:

  Please pull from:
    git://server/path branch

And he cuts and pastes into the command line:

  git pull git://server/path branch

Now, this syntax isn't available for git-clone, because git-clone puts the 
optional directory to create after the URL. But, in an ideal world, this 
is how it would work; you could see a pull request, and just type "git 
some-command <paste>".

I think I already suggested this to Carl once, but if you 
forget about 'git clone' in this case (or any other cases), your
example would just work.

	$ git init
        $ git pull git://server/path branch

It works for Linus's usage, where he expects to get all the info again 
next time there's more useful stuff. I don't think this configures things 
so that:

	$ git init
	$ git pull git://server/path branch
	... wait a couple of weeks and forget the URL ...
	$ git pull

works. (Although I haven't actually checked, so I could be totally wrong)

	-Daniel
*This .sig left intentionally blank*