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

Re: [PATCH v2] git-send-email.perl: fix In-Reply-To for second and subsequent patches

From
Antonio Ospite <ospite@studenti.unina.it>
Date
Oct 26, 2010, 13:50 UTC
Message-ID
<20101026155043.f7e24764.ospite@studenti.unina.it>
In-Reply-To
<20101020004533.b64d446c.ospite@studenti.unina.it>

On Wed, 20 Oct 2010 00:45:33 +0200 Antonio Ospite <ospite@studenti.unina.it> wrote:

Show 5 quoted lines
> On Tue, 19 Oct 2010 11:26:33 -0700
> Junio C Hamano <gitster@pobox.com> wrote:
> 
> Thanks for commenting Junio.
>

Junio, did you see the comments inlined in the previous message? Maybe the "Thanks" line above made you think that there were no more comments?

If you saw them and agree with what I wrote then I am sending a v3 in some days adding just the doc updates.

Thanks,
   Antonio
-- 
Antonio Ospite
http://ao2.it

PGP public key ID: 0x4553B001

A: Because it messes up the order in which people normally read text.
   See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
Previous: Antonio OspiteNext: Antonio Ospite
Message 8 of 19 in “git-send-email.perl: fix In-Reply-To for second and subsequent patches”
  1. git-send-email.perl: fix In-Reply-To for second and subsequent patchesAntonio Ospite, Oct 14, 2010
  2. Jonathan NiederOct 14, 2010
  3. Antonio OspiteOct 15, 2010
  4. git-send-email.perl: fix In-Reply-To for second and subsequent patchesAntonio Ospite, Oct 19, 2010
  5. Junio C HamanoOct 19, 2010
  6. Junio C HamanoOct 19, 2010
  7. Antonio OspiteOct 19, 2010
  8. Antonio OspiteOct 26, 2010
  9. git-send-email.perl: make initial In-Reply-To apply only to first emailAntonio Ospite, Nov 5, 2010
  10. Matthieu MoyNov 5, 2010
  11. Junio C HamanoNov 9, 2010
  12. Antonio OspiteNov 10, 2010
  13. Junio C HamanoNov 10, 2010
  14. [PATCHi v4] git-send-email.perl: make initial In-Reply-To apply only to first emailAntonio Ospite, Nov 12, 2010
  15. Junio C HamanoNov 12, 2010
  16. Junio C HamanoNov 12, 2010
  17. Antonio OspiteNov 12, 2010
  18. Jonathan NiederNov 5, 2010
  19. Antonio OspiteNov 8, 2010

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.