From: "Sean" <seanlkml@sympatico.ca>
To: "Junio C Hamano" <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC] adding merge-node to parent lines in a commit
Date: Sun, 15 May 2005 18:47:43 -0400 (EDT) [thread overview]
Message-ID: <1522.10.10.10.24.1116197263.squirrel@linux1> (raw)
In-Reply-To: <7v64xkqfqg.fsf@assigned-by-dhcp.cox.net>
On Sun, May 15, 2005 6:36 pm, Junio C Hamano said:
>>>>>> "S" == Sean <seanlkml@sympatico.ca> writes:
>
> S> Yes, it's pretty basic unless i'm overlooking something:
>
> Rn---\
> Mn
> Mn-1
> Rn-1 |
> Rn-2 |
> Rn-3--/
> Initial
>
> S> So for this particular case it's rather simple, the Rn merge
> S> node would have:
>
> S> parent Rn-1 (ommitted)
> S> parent Mn Rn-3
>
> Isn't that something you can obtain by scanning the parents and
> running merge-base across them without recording it in the
> commit?
Yes it is, and i was mistaken to think it gave more information. It would
shave some time off history traversal, but nothing else.
Sean
prev parent reply other threads:[~2005-05-15 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 21:22 [RFC] adding merge-node to parent lines in a commit Sean
2005-05-15 21:30 ` Junio C Hamano
2005-05-15 22:07 ` Sean
2005-05-15 22:36 ` Junio C Hamano
2005-05-15 22:47 ` Sean [this message]
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=1522.10.10.10.24.1116197263.squirrel@linux1 \
--to=seanlkml@sympatico.ca \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.