From: Jon Seymour <jon.seymour@gmail.com>
To: git@vger.kernel.org
Cc: Linus Torvalds <torvalds@osdl.org>
Subject: Re: [EXPERIMENTAL PATCH] O(n) bisection algorithm
Date: Thu, 30 Jun 2005 19:03:51 +1000 [thread overview]
Message-ID: <2cfc4032050630020359c76147@mail.gmail.com> (raw)
In-Reply-To: <20050630081135.27577.qmail@blackcubes.dyndns.org>
BTW: just in case you are wondering what these variables are for and
why they and the associated code is there...
> +static struct commit_list * topological_order = NULL;
> +static struct commit_list ** t_o_tail = &topological_order;
They are not required. This was a remnant of a previous version that
used the --merge-order code to obtain the topological order. Of
course, the final submission will remove this redundant code.
jon.
prev parent reply other threads:[~2005-06-30 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 8:11 [EXPERIMENTAL PATCH] O(n) bisection algorithm Jon Seymour
2005-06-30 9:03 ` 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=2cfc4032050630020359c76147@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=git@vger.kernel.org \
--cc=jon@blackcubes.dyndns.org \
--cc=torvalds@osdl.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).