From: Brian Gernhardt <brian@gernhardtsoftware.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Charles Bailey <charles@hashpling.org>,
Theodore Ts'o <tytso@mit.edu>
Subject: Re: Why does git-mergetool use /dev/tty?
Date: Mon, 23 Aug 2010 21:58:23 -0400 [thread overview]
Message-ID: <D4C0AFB5-EC8C-44B6-9280-9915DE224CB6@gernhardtsoftware.com> (raw)
In-Reply-To: <20100824015337.GC17406@burratino>
On Aug 23, 2010, at 9:53 PM, Jonathan Nieder wrote:
> Brian Gernhardt wrote:
>
>> Why does git-mergetool ignore the provided STDIN and STDOUT when not given a path to merge?
>
> See af314714 (mergetool: Remove explicit references to /dev/tty,
> 2010-08-20) in pu.
>
> Hope that helps,
It does really help, actually. One thing removed from my TODO.
~~ Brian
next prev parent reply other threads:[~2010-08-24 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 1:49 Why does git-mergetool use /dev/tty? Brian Gernhardt
2010-08-24 1:53 ` Jonathan Nieder
2010-08-24 1:58 ` Brian Gernhardt [this message]
2010-08-24 6:43 ` Charles Bailey
2010-08-24 7:04 ` Brian Gernhardt
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=D4C0AFB5-EC8C-44B6-9280-9915DE224CB6@gernhardtsoftware.com \
--to=brian@gernhardtsoftware.com \
--cc=charles@hashpling.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=tytso@mit.edu \
/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).