All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Aveling <bena.001@optusnet.com.au>
To: Junio C Hamano <gitster@pobox.com>
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: Fri, 20 Sep 2013 08:46:17 +1000	[thread overview]
Message-ID: <523B7EB9.9050809@optusnet.com.au> (raw)
In-Reply-To: <523AF8EA.6080307@optusnet.com.au>

On 19/9/13 23:15, Ben Aveling wrote:
> On 18/9/13 05:20, Junio C Hamano wrote:
>> Lukas Fleischer <git@cryptocrack.de> writes:
>>> why do we allow running git-checkout(1)
>>> from a subdirectory?
>> We may want to check the condition and forbid such a checkout.
> It would probably make sense.
> It might also make sense to relax the check in git bisect somewhat. 
> Currently, even "git bisect help" insists that "You need to run this 
> command from the toplevel of the working tree."

Probably also worth pointing out that whether or not the current shell 
is at toplevel, there can be other processes active in subdirectories.

     Regards, Ben

  reply	other threads:[~2013-09-19 22:46 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 [this message]
2013-09-19 23:04           ` Junio C Hamano
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=523B7EB9.9050809@optusnet.com.au \
    --to=bena.001@optusnet.com.au \
    --cc=git@cryptocrack.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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.