threads / discuss / 1013

Re: Updated git HOWTO for kernel hackers

Subject: Re: Updated git HOWTO for kernel hackers

## tl;dr

3 messages between Jun 23, 2005 and Oct 1, 2005.

replies: 2people: 2as markdown or json

Horst von Brand· Jun 23, 2005, 14:31 UTC · lore

Jeff Garzik <jgarzik@pobox.com> said:

Show 18 quoted lines

> Linus Torvalds wrote:
> > 	rsync -r --ignore-existing repo/refs/tags/ .git/refs/tags/
> > 
> > See? What's your complaint with just doing that?
> 
> No complaint with that operation.  The complaint is that it's an 
> additional operation.  Re-read what Greg said:
> 
> > Is there some reason why git doesn't pull the
> > tags in properly when doing a merge?  Chris and I just hit this when I
> > pulled his 2.6.12.1 tree and and was wondering where the tag went.
> 
> Multiple users -- not just me -- would prefer that git-pull-script 
> pulled the tags, too.
> 
> Suggested solution:  add '--tags' to git-pull-script 
> (git-fetch-script?), which calls
> 	rsync -r --ignore-existing repo/refs/tags/ .git/refs/tags/

I don't think either is really a solution. IMHO there should be a distinction between "official tags" (that get passed around together with everything else) and "private tags" for everybodys own home use (that could be passed around, but only explicitly). Plus the possibility to erase, move, &c private tags, and perhaps upgrade them to official status (thus setting them in stone).

-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513

Horst von Brand· Sep 30, 2005, 18:13 UTC · lore

Re: [howto] Kernel hacker's guide to git, updated

Jeff Garzik <jgarzik@pobox.com> wrote:

Show 6 quoted lines

> Thanks for all the comments.  I just updated the KHGtG with the
> feedback I received.  Go to
> 
> 	http://linux.yyz.us/git-howto.html
> 
> and click reload.  Continued criticism^H^H^Hcomments welcome!

- To know the current branch, "git branch" is enough (the one '*'-ed)
- rsync(1) a repository is dangerous, it might catch it in the middle of
  a update and give you an incomplete/messed up copy. Repeat rsync until no
  change, perhaps?
- I understand "git checkout -f" blows away any local changes, no questions
  asked. Not very nice to suggest that to a newbie...

Thanks for the docu!

-- 
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513

Jeff Garzik· Oct 1, 2005, 00:17 UTC · re: Horst von Brand · lore

Re: [howto] Kernel hacker's guide to git, updated

Horst von Brand wrote:

Show 11 quoted lines

> Jeff Garzik <jgarzik@pobox.com> wrote:
> 
>>Thanks for all the comments.  I just updated the KHGtG with the
>>feedback I received.  Go to
>>
>>	http://linux.yyz.us/git-howto.html
>>
>>and click reload.  Continued criticism^H^H^Hcomments welcome!
> 
> 
> - To know the current branch, "git branch" is enough (the one '*'-ed)

Click reload, this is already mentioned.

> - rsync(1) a repository is dangerous, it might catch it in the middle of
>   a update and give you an incomplete/messed up copy. Repeat rsync until no
>   change, perhaps?

Usually that's just unlucky. I have caught kernel.org in the middle of a sync once, maybe twice.

> - I understand "git checkout -f" blows away any local changes, no questions
>   asked. Not very nice to suggest that to a newbie...

I constantly run into problems if I -do not- use the "-f" flag. I habitually use it at all times, now.

Thanks,

	Jeff