From: Christian Couder <christian.couder@gmail.com>
To: Trevor Saunders <tbsaunde@tbsaunde.org>
Cc: Stefan Beller <sbeller@google.com>,
Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] bisect: print abbrev sha1 for first bad commit
Date: Wed, 13 May 2015 15:24:40 +0200 [thread overview]
Message-ID: <CAP8UFD1eA8U8DnjY2qqCxR5HEtd3EzFJ0Ck8CNrWAh_25YyaXQ@mail.gmail.com> (raw)
In-Reply-To: <20150512234014.GE31257@tsaunders-iceball.corp.tor1.mozilla.com>
On Wed, May 13, 2015 at 1:40 AM, Trevor Saunders <tbsaunde@tbsaunde.org> wrote:
>
> my sense is that the division between git-bisect.sh and bisect--helper.c
> isn't really great and could already use refactoring so I suspect it'd
> be a fair amount of work.
About the division between git-bisect.sh and bisect--helper.c, yeah I
started converting git-bisect.sh into C code, but haven't finished
that.
prev parent reply other threads:[~2015-05-13 13:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 23:46 [PATCH] bisect: print abbrev sha1 for first bad commit Trevor Saunders
2015-05-09 0:29 ` Stefan Beller
2015-05-09 2:03 ` Trevor Saunders
2015-05-09 4:07 ` Jeff King
2015-05-10 23:12 ` Trevor Saunders
2015-05-11 1:10 ` Jeff King
2015-05-11 4:33 ` Junio C Hamano
2015-05-11 7:38 ` Christian Couder
2015-05-11 16:54 ` Junio C Hamano
2015-05-11 18:17 ` Trevor Saunders
2015-05-11 18:28 ` Stefan Beller
2015-05-12 9:21 ` Christian Couder
2015-05-12 17:11 ` Junio C Hamano
2015-05-12 20:43 ` Christian Couder
2015-05-12 20:58 ` Stefan Beller
2015-05-12 23:40 ` Trevor Saunders
2015-05-13 13:24 ` Christian Couder [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=CAP8UFD1eA8U8DnjY2qqCxR5HEtd3EzFJ0Ck8CNrWAh_25YyaXQ@mail.gmail.com \
--to=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=sbeller@google.com \
--cc=tbsaunde@tbsaunde.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).