Re: [PATCH] Do not fetch tags on new shallow clones
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jan 5, 2012, 05:57 UTC
- Message-ID
- <7vfwfuofnk.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <CAJo=hJvL2ebziPw=0q-e=G3WFEvEKtFR2xMFMiquSyrHJDradA@mail.gmail.com>
Shawn Pearce <spearce@spearce.org> writes:
Show 7 quoted lines
> 2012/1/4 Junio C Hamano <gitster@pobox.com>: >> Nguyễn Thái Ngọc Duy <pclouds@gmail.com> writes: >>> We should also fetch tags that reference to downloaded objects. >> >> I do not think this has much merit. > > I disagree. ...
No, you don't. Because...
> ... Its useful because cloning a branch immediately after it > has been tagged for a release should have `git describe` provide back > the name of the release from the tag (assuming of course no new > commits were made since the tag).
... this is a natural extension of ...
Show 6 quoted lines
>> It also is my understanding that the shallow hack is almost always used >> with a depth of one, not a range, like "git archive | tar xf -", so if >> anything, I would say a single-branch cloning has much higher priority >> than following tags. > > I think I agree with you on priority of work effort. ...
... this thing, once you have a "single ref only" stuff working. After Linus announces that he released 3.2, you would do the poor emulation of "git archive | tar xf -" with something like:
git clone --single=v3.2 --shallow $there linux-3.2
and your "git describe" should fall out as a natural consequence out of everything else, without the usual "tag following" semantics, no?