From: Junio C Hamano <gitster@pobox.com>
To: Ben Aveling <bena.001@optusnet.com.au>
Cc: Lukas Fleischer <git@cryptocrack.de>, "Burton\,
Ross" <ross.burton@intel.com>,
git@vger.kernel.org
Subject: Re: Bisect needing to be at repo top-level?
Date: Thu, 19 Sep 2013 16:04:31 -0700 [thread overview]
Message-ID: <xmqqpps4qups.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <523B7EB9.9050809@optusnet.com.au> (Ben Aveling's message of "Fri, 20 Sep 2013 08:46:17 +1000")
Ben Aveling <bena.001@optusnet.com.au> writes:
> Probably also worth pointing out that whether or not the current shell
> is at toplevel, there can be other processes active in subdirectories.
That is not something we have control over anyway.
next prev parent reply other threads:[~2013-09-19 23:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 16:31 Bisect needing to be at repo top-level? Burton, Ross
2013-09-17 17:27 ` Junio C Hamano
2013-09-17 17:58 ` Lukas Fleischer
2013-09-17 19:20 ` Junio C Hamano
2013-09-19 13:15 ` Ben Aveling
2013-09-19 22:46 ` Ben Aveling
2013-09-19 23:04 ` Junio C Hamano [this message]
2013-10-09 18:27 ` Stefan Beller
2013-10-09 18:55 ` Jeff King
2013-10-09 19:01 ` Stefan Beller
2013-09-17 18:38 ` Burton, Ross
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=xmqqpps4qups.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=bena.001@optusnet.com.au \
--cc=git@cryptocrack.de \
--cc=git@vger.kernel.org \
--cc=ross.burton@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.