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

Re: [PATCH] Avoid the use of backslash-at-eol in pack-objects usage string.

From
Thiago Farina <tfransosi@gmail.com>
Date
Sep 17, 2009, 22:06 UTC
Message-ID
<a4c8a6d00909171506l6c4b6a49i22d7b337a0c6cfa2@mail.gmail.com>
In-Reply-To
<7vvdjhgrjv.fsf@alter.siamese.dyndns.org>
On Thu, Sep 17, 2009 at 7:00 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 13 quoted lines
> Thiago Farina <tfransosi@gmail.com> writes:
>
>> +static const char pack_usage[] =
>> +  "git pack-objects [{ -q | --progress | --all-progress }] \n"
>> +  "        [--max-pack-size=N] [--local] [--incremental] \n"
>> +  "        [--window=N] [--window-memory=N] [--depth=N] \n"
>> +  "        [--no-reuse-delta] [--no-reuse-object] [--delta-base-offset] \n"
>> +  "        [--threads=N] [--non-empty] [--revs [--unpacked | --all]*] [--reflog] \n"
>> +  "        [--stdout | base-name] [--include-tag] \n"
>> +  "        [--keep-unreachable | --unpack-unreachable] \n"
>> +  "        [<ref-list | <object-list]";
>
> Do you still want to keep the trailing whitespace on these lines?

I did this to maintain the same output of the old string, but if you want I can change, what you suggest?

Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 7 in “Avoid the use of backslash-at-eol in pack-objects usage string.”
  1. Avoid the use of backslash-at-eol in pack-objects usage string.Thiago Farina, Sep 17, 2009
  2. Junio C HamanoSep 17, 2009
  3. Thiago FarinaSep 17, 2009
  4. Junio C HamanoSep 18, 2009
  5. Thiago FarinaSep 18, 2009
  6. Junio C HamanoSep 18, 2009
  7. Thiago FarinaSep 18, 2009

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.