git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] git help -w should not create nohup.out

From
Dmitry Potapov <dpotapov@gmail.com>
Date
Feb 8, 2008, 10:33 UTC
Message-ID
<20080208103307.GT30368@dpotapov.dyndns.org>
In-Reply-To
<7vhcgkm7yy.fsf@gitster.siamese.dyndns.org>
On Thu, Feb 07, 2008 at 07:40:21PM -0800, Junio C Hamano wrote:
Show 27 quoted lines
> 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
Previous: Dmitry PotapovNext: Dmitry Potapov
Message 6 of 11 in “git help -w should not create nohup.out”
  1. git help -w should not create nohup.outDmitry Potapov, Feb 8, 2008
  2. Johannes SchindelinFeb 8, 2008
  3. Junio C HamanoFeb 8, 2008
  4. Christian CouderFeb 8, 2008
  5. Dmitry PotapovFeb 8, 2008
  6. Dmitry PotapovFeb 8, 2008
  7. remove "nohup" from git-help--browseDmitry Potapov, Feb 8, 2008
  8. Christian CouderFeb 9, 2008
  9. Dmitry PotapovFeb 9, 2008
  10. Junio C HamanoFeb 10, 2008
  11. Johannes SchindelinFeb 10, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.