From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: git@vger.kernel.org, John Tapsell <johnflux@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 09/10] bisect: implement "read_bisect_paths" to read paths in "$GIT_DIR/BISECT_NAMES"
Date: Wed, 25 Mar 2009 23:49:26 -0700 [thread overview]
Message-ID: <7vwsacrd6x.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 20090326055559.743cb502.chriscool@tuxfamily.org
Christian Couder <chriscool@tuxfamily.org> writes:
> This is needed because "git bisect--helper" must read bisect paths
> in "$GIT_DIR/BISECT_NAMES", so that a bisection can be performed only
> on commits that touches paths in this file.
>
> Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Again, very nice.
> bisect.c | 56 +++++++++++++++++++++++++++++++++++++++++++++++---------
> 1 files changed, 47 insertions(+), 9 deletions(-)
>
> diff --git a/bisect.c b/bisect.c
> index ce62696..a6fd826 100644
> --- a/bisect.c
> +++ b/bisect.c
> @@ -4,6 +4,7 @@
> #include "revision.h"
> #include "refs.h"
> #include "list-objects.h"
> +#include "quote.h"
> #include "bisect.h"
>
>
> @@ -424,6 +425,33 @@ static int read_bisect_refs(void)
> return for_each_bisect_ref(register_ref, NULL);
> }
>
> +void read_bisect_paths()
> +{
> + struct strbuf str = STRBUF_INIT;
> + const char *filename = git_path("BISECT_NAMES");
> + FILE *fp = fp = fopen(filename, "r");
s/= fp //;
next prev parent reply other threads:[~2009-03-26 6:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 4:55 [PATCH 09/10] bisect: implement "read_bisect_paths" to read paths in "$GIT_DIR/BISECT_NAMES" Christian Couder
2009-03-26 6:49 ` Junio C Hamano [this message]
2009-03-27 0:18 ` Christian Couder
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=7vwsacrd6x.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=johnflux@gmail.com \
/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).