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

Re: [PATCH 1/2] format-patch: fix dashdash usage

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Nov 28, 2009, 11:18 UTC
Message-ID
<94a0d4530911280318nd6ea6d4s7ee159fe173a3f2f@mail.gmail.com>
In-Reply-To
<7vhbsg25sb.fsf@alter.siamese.dyndns.org>
On Fri, Nov 27, 2009 at 2:03 AM, Junio C Hamano <gitster@pobox.com> wrote:
>  (0) take your patch with an updated message (eh, that is not "next step"
>     but the "first step");

I guess it depends of what is the "fist step". To me the "first step" is realizing there's a problem. First patch submission is already many steps afterwards.

But sure, I'll do this next step :)
>  (1) make --full-diff implicit and default of format-patch (--no-full-diff
>     could be supported _if_ somebody can argue successfully why limiting
>     the diff is also a useful thing to do); and
I started writing this patch but it turns out there's no --no-full-diff.
>  (2) document clearly that format-patch takes optional pathspecs, and in
>     what situation they are useful.

I guess this would have to be done in multiple places so it might take me some time.

Cheers.
-- 
Felipe Contreras
Previous: Junio C HamanoNext: Junio C Hamano
Message 8 of 11 in “format-patch: fix dashdash”
  1. 0/2 format-patch: fix dashdashFelipe Contreras, Nov 26, 2009
  2. 1/2 format-patch: fix dashdash usageFelipe Contreras, Nov 26, 2009
  3. Junio C HamanoNov 26, 2009
  4. Felipe ContrerasNov 26, 2009
  5. Junio C HamanoNov 26, 2009
  6. Felipe ContrerasNov 26, 2009
  7. Junio C HamanoNov 27, 2009
  8. Felipe ContrerasNov 28, 2009
  9. Junio C HamanoNov 26, 2009
  10. Björn SteinbrinkNov 26, 2009
  11. 2/2 format-patch: add test for dashdashFelipe Contreras, Nov 26, 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.