From: Jon Seymour <jon.seymour@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git-rev-list --merge-order resynched with Linus' head
Date: Sun, 5 Jun 2005 17:33:59 +1000 [thread overview]
Message-ID: <2cfc4032050605003345e624da@mail.gmail.com> (raw)
In-Reply-To: <2cfc403205060500323de294dc@mail.gmail.com>
This latest revision of my merge-order patch adds support for
git-rev-list arguments of the form:
git-rev-list --merge-order a b c ^x ^y ^z
I believe the output is functionally equivalent to the existing
algorithm, though sorted differently. Please let me know if you find a
case where this is not so.
jon.
next prev parent reply other threads:[~2005-06-05 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-05 7:23 [PATCH] git-rev-list --merge-order resynched with Linus' head jon
[not found] ` <2cfc403205060500323de294dc@mail.gmail.com>
2005-06-05 7:33 ` Jon Seymour [this message]
2005-06-05 12:55 ` Jon Seymour
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=2cfc4032050605003345e624da@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=jon@blackcubes.dyndns.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).