From: Dmitry Potapov <dpotapov@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Christian Couder <chriscool@tuxfamily.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] git help -w should not create nohup.out
Date: Fri, 8 Feb 2008 13:33:07 +0300 [thread overview]
Message-ID: <20080208103307.GT30368@dpotapov.dyndns.org> (raw)
In-Reply-To: <7vhcgkm7yy.fsf@gitster.siamese.dyndns.org>
On Thu, Feb 07, 2008 at 07:40:21PM -0800, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > Hi,
> >
> > On Fri, 8 Feb 2008, Dmitry Potapov wrote:
> >
> >> git-help--browse uses 'nohup' to launch some browsers.
> >
> > Why?
> >
> > "nohup" should be used to start a program that should persist even after
> > you logged out. I fail to see how this should be sensible for "git help
> > -w". So "off with the head", uh, do away with the "nohup", I say!
>
> True. Christian, what was the reason you added nohup?
> I would imagine if you did this:
>
> (1) open a new xterm;
>
> (2) in that xterm, run the browser, perhaps from
> git-help--browse, but without nohup, in the
> background;
>
> (3) exit the terminal
>
> then the browser might get upset, losing its controlling
> terminal.
I also thought so, therefore, I suggested to redict the output to
/dev/null instead of removing "nohup", but now after some testing,
it seems there is no need for "nohup" here. So, unless Christian
has a good reason for "nohup", I agree with Johannes that "nohup"
should be removed.
Dmitry
next prev parent reply other threads:[~2008-02-08 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 1:33 [PATCH] git help -w should not create nohup.out Dmitry Potapov
2008-02-08 1:55 ` Johannes Schindelin
2008-02-08 3:40 ` Junio C Hamano
2008-02-08 5:37 ` Christian Couder
2008-02-08 11:25 ` Dmitry Potapov
2008-02-08 10:33 ` Dmitry Potapov [this message]
2008-02-08 20:36 ` [PATCH] remove "nohup" from git-help--browse Dmitry Potapov
2008-02-09 5:53 ` Christian Couder
2008-02-09 20:03 ` Dmitry Potapov
2008-02-10 2:02 ` Junio C Hamano
2008-02-10 2:06 ` Johannes Schindelin
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=20080208103307.GT30368@dpotapov.dyndns.org \
--to=dpotapov@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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).