Re: [PATCH] Proof-of-concept patch to remember what the detached HEAD was
- From
Daniel Barkalow <barkalow@iabervon.org>
- Date
- Oct 15, 2009, 19:22 UTC
- Message-ID
- <alpine.LNX.2.00.0910151517070.32515@iabervon.org>
- In-Reply-To
- <alpine.LFD.2.00.0910151504510.20122@xanadu.home>
On Thu, 15 Oct 2009, Nicolas Pitre wrote:
Show 20 quoted lines
> On Thu, 15 Oct 2009, Daniel Barkalow wrote: > > > I think the description used in CVS and SVN (and, I think, others) is that > > you're not at the HEAD revision. I think they both account for the state > > where you've checked out the revision by number that's the latest > > revision, but you still can't grow the branch because you can't > > simultaneously stay on r1000 (as requested explicitly) and add a new > > commit. > > > > So maybe the right explanation is: > > > > $ git checkout master; git branch > > * master > > $ git checkout origin/master; git branch > > * origin/master (not at head) > > $ git checkout 123cafe^5; git branch > > * 123cafe^5 (not at head) > > I think this is wrong. Git has multiple heads, and insisting on "not at > head" would be extremely confusing.
Maybe "(not at a head)"? Git does have multiple heads, but what's checked out isn't one of them, and that's actually the point.
-Daniel *This .sig left intentionally blank*