From: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
To: git@vger.kernel.org
Subject: Re: [PATCH] Bisect: fix calculation of the number of suspicious revisions
Date: Wed, 21 Mar 2007 22:34:50 +0100 [thread overview]
Message-ID: <20070321213450.GB17632@informatik.uni-freiburg.de> (raw)
In-Reply-To: <20070321210454.GA2844@lala>
Hello,
Uwe Kleine-König wrote:
> mv "$GIT_DIR/refs/heads/new-bisect" "$GIT_DIR/refs/heads/bisect" &&
independant of my suggested patch, I wonder if that line should better
use update-ref. (This line is older than update-ref.)
Best regards
Uwe
--
Uwe Kleine-König
$ dc -e "5735816763073014741799356604682P"
next prev parent reply other threads:[~2007-03-21 21:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-16 16:14 [BUG] bisecting miscounts revisions left to test Uwe Kleine-König
2007-03-17 0:50 ` Johannes Schindelin
2007-03-17 13:46 ` Uwe Kleine-König
2007-03-17 14:12 ` [PATCH] calculate the maximal number of revisions " Uwe Kleine-König
2007-03-17 17:49 ` Johannes Schindelin
2007-03-17 19:58 ` Uwe Kleine-König
2007-03-21 21:04 ` [PATCH] Bisect: fix calculation of the number of suspicious revisions Uwe Kleine-König
2007-03-21 21:23 ` Junio C Hamano
2007-03-21 21:39 ` Uwe Kleine-König
2007-03-21 21:34 ` Uwe Kleine-König [this message]
2007-03-21 21:49 ` Junio C Hamano
2007-03-21 22:27 ` Linus Torvalds
2007-03-22 1:19 ` Junio C Hamano
2007-03-22 1:43 ` [PATCH] bisect: show the maximal number of commits to be tested Johannes Schindelin
2007-03-22 2:05 ` Junio C Hamano
2007-03-22 2:15 ` Johannes Schindelin
2007-03-22 6:36 ` [PATCH 1/2] git-rev-list: add --bisect-vars option Junio C Hamano
2007-03-22 6:42 ` [PATCH 2/2] git-rev-list --bisect: optimization Junio C Hamano
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=20070321213450.GB17632@informatik.uni-freiburg.de \
--to=ukleinek@informatik.uni-freiburg.de \
--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).