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

Re: [PATCH v2 2/9] Documentation/git-send-pack.txt: Flow long synopsis line

From
Dave Borowitz <dborowitz@google.com>
Date
Aug 19, 2015, 19:59 UTC
Message-ID
<CAD0k6qRtXX3OqeQF_USwiNYA-y+92X65MSJqPKjhNjGka9QXBw@mail.gmail.com>
In-Reply-To
<xmqqtwrv8328.fsf@gitster.dls.corp.google.com>
On Wed, Aug 19, 2015 at 3:56 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 26 quoted lines
> Dave Borowitz <dborowitz@google.com> writes:
>
>> Signed-off-by: Dave Borowitz <dborowitz@google.com>
>> ---
>>  Documentation/git-send-pack.txt | 3 ++-
>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/git-send-pack.txt b/Documentation/git-send-pack.txt
>> index b5d09f7..6affff6 100644
>> --- a/Documentation/git-send-pack.txt
>> +++ b/Documentation/git-send-pack.txt
>> @@ -9,7 +9,8 @@ git-send-pack - Push objects over Git protocol to another repository
>>  SYNOPSIS
>>  --------
>>  [verse]
>> -'git send-pack' [--all] [--dry-run] [--force]
>> [--receive-pack=<git-receive-pack>] [--verbose] [--thin] [--atomic]
>> [<host>:]<directory> [<ref>...]
>> +'git send-pack' [--all] [--dry-run] [--force] [--receive-pack=<git-receive-pack>]
>> +             [--verbose] [--thin] [--atomic] [<host>:]<directory> [<ref>...]
>>
>>  DESCRIPTION
>>  -----------
>
> As can be expected from the Subject: line, this patch is
> line-wrapped and does not apply ;-)

I produced the patch with "git format-patch --subject-prefix='PATCH v2' --cover-letter @{u}.." and mailed with "git send-email --to=git@vger.kernel.org,gitster@pobox.com 0*.patch"; is there a way that would have preserved whitespace better?

> I've done a trivial fix-up and took the liberty of making the result
> of this step into three lines, not two.  That would make 3/9 look
> more trivial.
Ok by me.
> Thanks.
Previous: Junio C HamanoNext: Junio C Hamano
Message 5 of 19 in “Flags and config to sign pushes by default”
  1. 0/9 Flags and config to sign pushes by defaultDave Borowitz, Aug 19, 2015
  2. 1/9 Documentation/git-push.txt: Document when --signed may failDave Borowitz, Aug 19, 2015
  3. 2/9 Documentation/git-send-pack.txt: Flow long synopsis lineDave Borowitz, Aug 19, 2015
  4. Junio C HamanoAug 19, 2015
  5. Dave BorowitzAug 19, 2015
  6. Junio C HamanoAug 19, 2015
  7. Junio C HamanoSep 11, 2015
  8. 3/9 Documentation/git-send-pack.txt: Document --signedDave Borowitz, Aug 19, 2015
  9. 4/9 gitremote-helpers.txt: Document pushcert optionDave Borowitz, Aug 19, 2015
  10. 5/9 transport: Remove git_transport_options.push_certDave Borowitz, Aug 19, 2015
  11. 6/9 config.c: Expose git_parse_maybe_boolDave Borowitz, Aug 19, 2015
  12. 7/9 builtin/send-pack.c: Use option parsing APIDave Borowitz, Aug 19, 2015
  13. Stefan BellerAug 19, 2015
  14. Dave BorowitzAug 19, 2015
  15. Jeff KingAug 21, 2015
  16. 8/9 Support signing pushes iff the server supports itDave Borowitz, Aug 19, 2015
  17. Junio C HamanoAug 19, 2015
  18. Dave BorowitzAug 19, 2015
  19. 9/9 Add a config option push.gpgSign for default signed pushesDave Borowitz, Aug 19, 2015

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.