git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Seymour <jon.seymour@gmail.com>
To: git@vger.kernel.org
Subject: Re: Heads up on work in progress - was: [PATCH 2/2] Add support ... [rev 11]
Date: Sat, 11 Jun 2005 15:31:41 +1000	[thread overview]
Message-ID: <2cfc4032050610223112803863@mail.gmail.com> (raw)
In-Reply-To: <2cfc4032050610222853a882b7@mail.gmail.com>

> 2. improve separation of concerns between rev-list.c and commit-graph.c
>    * commit-graph.c will understand everything about incremental graph
> traversals, including merge order search and "localized" perspectives
>    * rev-list.c will be responsible for output limiting [ that is:
> stopping the traversal according to user-defined (e.g. parameterised
> criteria) ]

That'd be - merge order _sort_.

jon.

      reply	other threads:[~2005-06-11  5:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-10  9:23 [PATCH 2/2] Add support for author-oriented git-rev-list switches [rev 11] Jon Seymour
2005-06-11  5:28 ` Heads up on work in progress - was: [PATCH 2/2] Add support ... " Jon Seymour
2005-06-11  5:31   ` Jon Seymour [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=2cfc4032050610223112803863@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).