From: Junio C Hamano <gitster@pobox.com>
To: lists@haller-berlin.de (Stefan Haller)
Cc: anatoly.borodin@gmail.com (Anatoly Borodin), git@vger.kernel.org
Subject: Re: Limitiations of git rebase --preserve-merges --interactive
Date: Fri, 23 Sep 2016 08:37:00 -0700 [thread overview]
Message-ID: <xmqqvaxm1vc3.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1mu13z0.1hye7bq1uqj26sM%lists@haller-berlin.de> (Stefan Haller's message of "Fri, 23 Sep 2016 12:40:29 +0200")
lists@haller-berlin.de (Stefan Haller) writes:
> Thanks, this is interesting; I'm having trouble understanding the tests
> though. Some of them use rebase -p -i, but I don't understand why they
> use -i, or why that even works in a test (i.e. why it doesn't open an
> editor).
Upon starting up, tests dot-source t/test-lib.sh file and it
unsets most of GIT_* environment variables to obtain a stable
testing environment that is not affected by things that testers
may have in their environment.
There is EDITOR=: in t/test-lib.sh, which was added in 2006 before
GIT_EDITOR was invented. That is the one in effect for git
subcommands that usually interacts with editors during the test,
unless specific tests further override it with test_set_editor
helper.
next prev parent reply other threads:[~2016-09-23 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 8:46 Limitiations of git rebase --preserve-merges --interactive Stefan Haller
2016-09-22 19:33 ` Anatoly Borodin
2016-09-22 19:48 ` Kevin Daudt
2016-09-22 20:54 ` Stefan Beller
2016-09-23 10:40 ` Stefan Haller
2016-09-23 21:13 ` Johannes Schindelin
2016-09-23 22:26 ` Stefan Beller
2016-09-22 21:04 ` Anatoly Borodin
2016-09-22 21:01 ` Anatoly Borodin
2016-09-22 21:08 ` Stefan Beller
2016-09-23 21:04 ` Johannes Schindelin
2016-09-23 10:40 ` Stefan Haller
2016-09-23 15:37 ` Junio C Hamano [this message]
2016-09-23 15:50 ` Stefan Haller
2016-09-23 19:24 ` Johannes Sixt
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqvaxm1vc3.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=anatoly.borodin@gmail.com \
--cc=git@vger.kernel.org \
--cc=lists@haller-berlin.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).