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

Re: [PATCH] Explain in --pid-file that using --inetd implies it automatically

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 29, 2007, 10:23 UTC
Message-ID
<7v7iner64l.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<zm0a1vw9.fsf@cante.net>
Jari Aalto <jari.aalto@cante.net> writes:
Show 15 quoted lines
> Junio C Hamano <gitster@pobox.com> writes:
>>> -	Save the process id in 'file'.
>>> +	Save the process id in 'file'. When `--inetd` is in use, this
>>> +        option is not needed.
>>
>> Is it "is not needed"?  I think you meant to say "is ignored",
>> IOW, no pid file is written.
>
> Corrected
>
>     git repository http://cante.net/~jaalto/git/git
>     Branch: git-daemon.txt+option--pid-file.collapse
>
>  Documentation/git-daemon.txt |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)

Phuleeeze. Try to apply what you sent out with "git am" and watch the resulting commit log message in horrors!

Hint. "Documentation/SubmittingPatches".
Thanks.  I'll do this by hand so no need to resend.
Show 15 quoted lines
>
> diff --git a/Documentation/git-daemon.txt b/Documentation/git-daemon.txt
> index f902161..861d68f 100644
> --- a/Documentation/git-daemon.txt
> +++ b/Documentation/git-daemon.txt
> @@ -124,7 +124,8 @@ OPTIONS
>         Detach from the shell. Implies --syslog.
>  
>  --pid-file=file::
> -       Save the process id in 'file'.
> +       Save the process id in 'file'. When `--inetd` is in use, this
> +        option is ignored.
>  
>  --user=user, --group=group::
>         Change daemon's uid and gid before entering the service loop.
Previous: Jari AaltoNext: Junio C Hamano
Message 4 of 5 in “Explain in --pid-file that using --inetd implies it automatically”
  1. Explain in --pid-file that using --inetd implies it automaticallyJari Aalto, Aug 29, 2007
  2. Junio C HamanoAug 29, 2007
  3. Jari AaltoAug 29, 2007
  4. Junio C HamanoAug 29, 2007
  5. git-daemon(1): assorted improvements.Junio C Hamano, Aug 29, 2007

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.