Re: What's cooking in git.git (Jan 2012, #08; Tue, 31)

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 10, 2012, 02:27 UTC
Message-ID: <7vsjijs9rq.fsf@alter.siamese.dyndns.org>
In-Reply-To: <7vlion3tr5.fsf@alter.siamese.dyndns.org>

Junio C Hamano <gitster@pobox.com> writes:

Show 24 quoted lines

> What's cooking in git.git (Jan 2012, #08; Tue, 31)
> --------------------------------------------------
> ...
> [Graduated to "master"]
>
> * nd/clone-detached (2012-01-24) 12 commits
>   (merged to 'next' on 2012-01-26 at 7b0cc8a)
>  + clone: fix up delay cloning conditions
>   (merged to 'next' on 2012-01-23 at bee31c6)
>  + push: do not let configured foreign-vcs permanently clobbered
>   (merged to 'next' on 2012-01-23 at 9cab64e)
>  + clone: print advice on checking out detached HEAD
>  + clone: allow --branch to take a tag
>  + clone: refuse to clone if --branch points to bogus ref
>  + clone: --branch=<branch> always means refs/heads/<branch>
>  + clone: delay cloning until after remote HEAD checking
>  + clone: factor out remote ref writing
>  + clone: factor out HEAD update code
>  + clone: factor out checkout code
>  + clone: write detached HEAD in bare repositories
>  + t5601: add missing && cascade
>
> "git clone" learned to detach the HEAD in the resulting repository when
> the source repository's HEAD does not point to a branch.

It turns out that this series, as a side effect, fixes a long-standing bug that the --branch option cannot be used with the --mirror option.

I am tempted to merge it also to 1.7.9.1 maintenance track. The issue is minor (you can always clone with --mirror and then switch the branch with "checkout") and it does not look like it warrants further backpointing to 1.7.8 and older releases, though.

Comments and/or objections?