From: Nicolas Pitre <nico@cam.org>
To: Rafael Garcia-Suarez <rgarciasuarez@gmail.com>
Cc: Chris Shoemaker <c.shoemaker@cox.net>,
Jakub Narebski <jnareb@gmail.com>,
geoffrey.russell@gmail.com, git@vger.kernel.org
Subject: Re: About detached heads
Date: Fri, 14 Mar 2008 11:19:37 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.00.0803141117040.2947@xanadu.home> (raw)
In-Reply-To: <b77c1dce0803140753w21515021u4541796d6e6934b@mail.gmail.com>
On Fri, 14 Mar 2008, Rafael Garcia-Suarez wrote:
> On 14/03/2008, Chris Shoemaker wrote:
> > This way you would get exactly:
> >
> > 1---2---3---4---5---3' <--- master <--- HEAD
> >
> >
> > While the 3' commit has the same contents as 3, it is a new, distinct
> > commit with its own history. Its commit message should explain why
> > you want to go from 5 back to the contents of 3.
>
> Just a small question -- does that mean that 3 and 3' share the same
> tree object ?
Yes. However, they don't share the same parent in the commit object, so
even if the commit text was the same and the time stamps were forced to
be the same, the commit 3' won't have the same SHA1.
Nicolas
next prev parent reply other threads:[~2008-03-14 15:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 9:46 About detached heads Geoff Russell
2008-03-14 9:51 ` Jonathan del Strother
2008-03-14 10:39 ` David Kågedal
2008-03-14 10:15 ` Wincent Colaiuta
2008-03-14 10:48 ` Matthieu Moy
2008-03-14 11:17 ` Wincent Colaiuta
2008-03-14 10:52 ` Jakub Narebski
2008-03-14 12:16 ` Sergei Organov
2008-03-14 12:28 ` Adam Piatyszek
2008-03-14 13:42 ` Chris Shoemaker
2008-03-14 14:53 ` Rafael Garcia-Suarez
2008-03-14 15:19 ` Nicolas Pitre [this message]
2008-03-14 15:21 ` Jakub Narebski
2008-03-14 17:53 ` Linus Torvalds
2008-03-14 18:37 ` Björn Steinbrink
2008-03-14 18:51 ` Linus Torvalds
2008-03-14 19:11 ` Jakub Narebski
2008-03-14 19:17 ` Sean
2008-03-14 23:43 ` Geoff Russell
2008-03-15 0:03 ` Jakub Narebski
2008-03-15 0:38 ` Nicolas Pitre
2008-03-15 2:03 ` Geoff Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.1.00.0803141117040.2947@xanadu.home \
--to=nico@cam.org \
--cc=c.shoemaker@cox.net \
--cc=geoffrey.russell@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=rgarciasuarez@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).