From: Hannu Koivisto <azure@iki.fi>
To: git@vger.kernel.org
Subject: Re: git bisect view's use of DISPLAY environment variable in Cygwin
Date: Wed, 29 Oct 2008 00:37:55 +0200 [thread overview]
Message-ID: <83iqrccpmk.fsf@kalahari.s2.org> (raw)
In-Reply-To: c07716ae0810281213k432d82d8i468f54ae03146b88@mail.gmail.com
"Christian Couder" <christian.couder@gmail.com> writes:
> On Tue, Oct 28, 2008 at 6:51 PM, Hannu Koivisto <azure@iki.fi> wrote:
>> "Christian Couder" <christian.couder@gmail.com> writes:
> We need at least a way to detect we are under Cygwin, because we won't
> change the current behavior for all platforms.
> Is checking for the CYGWIN environment variable enough?
No, because it may not be set. I would probably do it at compile
time using __CYGWIN__ definition. I don't know what's the status
of merging MSysGit with "official" git but I suppose that when that
happens, __MING32__ and/or _WIN32 or something would need to be
considered as well.
>>> You can use "git bisect view log" to use "git log" even if DISPLAY is set.
>>
>> I'd rather not use undocumented functionality ;)
>
> In this case you can use any "git log" option after "git bisect view"
> (for example: git bisect view -p).
I was implying that "log" after "git bisect view" is not documented
by git-bisect(1). "log" is not a "git log" option.
--
Hannu
next prev parent reply other threads:[~2008-10-28 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 16:28 git bisect view's use of DISPLAY environment variable in Cygwin Hannu Koivisto
2008-10-28 17:15 ` Christian Couder
2008-10-28 17:51 ` Hannu Koivisto
2008-10-28 19:13 ` Christian Couder
2008-10-28 22:37 ` Hannu Koivisto [this message]
2008-10-28 23:26 ` Hannu Koivisto
2008-10-29 0:46 ` Johannes Schindelin
2008-10-29 13:31 ` Hannu Koivisto
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=83iqrccpmk.fsf@kalahari.s2.org \
--to=azure@iki.fi \
--cc=git@vger.kernel.org \
/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).