From: "Sean" <seanlkml@sympatico.ca>
To: git@vger.kernel.org
Subject: [RFC] adding merge-node to parent lines in a commit
Date: Sun, 15 May 2005 17:22:27 -0400 (EDT) [thread overview]
Message-ID: <1282.10.10.10.24.1116192147.squirrel@linux1> (raw)
In-Reply-To:
Just a random thought presented for flamage... Would adding the merge
node to each "parent" line in merge nodes be workable?
parent SHA1-PARENT SHA1-MERGE-NODE
It's not exactly clear cut I guess, especially in the case of multi-parent
merges, but it would make descending the history slightly easier. It
would let you look at any merge, and know exactly which commits were
associated with that merge, without needing any repo-id or time
information. This information is needed at the time of merge anyway, so
recording it rather than leaving it to be calculated later makes some
sense. Comments?
Cheers,
Sean
next reply other threads:[~2005-05-15 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-15 21:22 Sean [this message]
2005-05-15 21:30 ` [RFC] adding merge-node to parent lines in a commit Junio C Hamano
2005-05-15 22:07 ` Sean
2005-05-15 22:36 ` Junio C Hamano
2005-05-15 22:47 ` Sean
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=1282.10.10.10.24.1116192147.squirrel@linux1 \
--to=seanlkml@sympatico.ca \
--cc=git@vger.kernel.org \
/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).