From: Junio C Hamano <gitster@pobox.com>
To: "Burton\, Ross" <ross.burton@intel.com>
Cc: git@vger.kernel.org
Subject: Re: Bisect needing to be at repo top-level?
Date: Tue, 17 Sep 2013 10:27:49 -0700 [thread overview]
Message-ID: <xmqqbo3rz7ca.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAJTo0LZ=bNNUc8O=bDDOp2vudsc_wL+-nqsXW5r1rq3H7M0e7Q@mail.gmail.com> (Ross Burton's message of "Tue, 17 Sep 2013 17:31:57 +0100")
"Burton, Ross" <ross.burton@intel.com> writes:
> Why does git-bisect need to be ran from the top level of the working
> tree? It sources git-sh-setup.sh which sets GIT_DIR, which
> git-bisect.sh then appears to consistently use. Is there a reason for
> needing to be at the top-level, or is this an old and redundant
> message?
A wild guess.
Imagine if you start from a subdirectory foo/ but the directory did
not exist in the older part of the history of the project. When
bisect needs to check out a revision that was older than the first
revision that introduced that subdirectory, what should happen?
Worse yet, if "foo" was a file in the older part of the history,
what should happen?
next prev parent reply other threads:[~2013-09-17 17:27 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 [this message]
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
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=xmqqbo3rz7ca.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--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.