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

Re: [PATCH v4] Thunderbird: fix appp.sh format problems

From
MSMarco Stornelli <marco.stornelli@gmail.com>
Date
Sep 4, 2012, 18:59 UTC
Message-ID
<50464FA8.3020104@gmail.com>
In-Reply-To
<7vd321dc0e.fsf@alter.siamese.dyndns.org>
Il 04/09/2012 17:49, Junio C Hamano ha scritto:
Show 31 quoted lines
> Marco Stornelli <marco.stornelli@gmail.com> writes:
>
>> 2012/9/4 Junio C Hamano <gitster@pobox.com>:
>>
>>> I would expect, at least when you are responding to an existing
>>> message, some of them are filled already (and if so, I think appp.sh
>>> wants to know exactly how, for example, has RFC2047 quoting already
>>> applied, or are we supposed to write in UTF-8 and let Thunderbird
>>> massage the contents when we give the file back to it?), and also
>>> there would appear In-Reply-To: field already filled (possibly there
>>> may be References: as well).
>>
>> Message reply is out of scope of my patch. The goal here is send a
>> patch, so the execution flow is to open a new message,
>> clik on external editor (configured properly), select patch file and
>> send. It was the scope of the old script and it is the scope of my
>> patch.
>
> I certainly can understand that you updated the script for that use
> case and that use case only, but given that the original tries very
> hard to preserve:
>
>   - what was in $HEADERS (by only replacing Subject);
>   - the recipients CC'ed in $HEADERS (by grabbing them into $CCS); and
>   - the body of the message in $BODY (i.e. what came after $SEP),
>
> I find it hard to believe that it was meant to work on a freshly
> created empty message and nothing else.  If people were depending on
> the recipients listed on Cc that are taken from $1 to be preserved,
> your patch will introduce a regression for them, no?
>

I think all the process is different. Current script rely on the user to fill Cc: and To: in message composition window, it does a union of what found in commit message as signed-off-by (adding own address in cc?!) and Cc (usually not filled in the commit message and we should even count acked-by, tested-by and so on). My vision of things: the user can create a patch *already* with all information using --to and --cc. If you want to add optional addresses, you can of course add them in the composition window. In addition, with this approach is really easy to use external script as get_maintainer.pl of linux kernel, load the patch and send, really easy. So I don't think it's a regression, it's only a change in the work flow.

Marco
Previous: Junio C HamanoNext: Junio C Hamano
Message 18 of 21 in “Thunderbird: fix appp.sh format problems”
  1. Thunderbird: fix appp.sh format problemsMarco Stornelli, Aug 31, 2012
  2. Junio C HamanoAug 31, 2012
  3. Marco StornelliSep 1, 2012
  4. Junio C HamanoSep 2, 2012
  5. Junio C HamanoAug 31, 2012
  6. Johannes SixtAug 31, 2012
  7. Marco StornelliSep 1, 2012
  8. Johannes SixtSep 1, 2012
  9. Marco StornelliSep 1, 2012
  10. Junio C HamanoSep 2, 2012
  11. Marco StornelliSep 3, 2012
  12. Marco StornelliSep 3, 2012
  13. Junio C HamanoSep 3, 2012
  14. Marco StornelliSep 4, 2012
  15. Junio C HamanoSep 4, 2012
  16. Marco StornelliSep 4, 2012
  17. Junio C HamanoSep 4, 2012
  18. Marco StornelliSep 4, 2012
  19. Junio C HamanoSep 4, 2012
  20. Marco StornelliSep 5, 2012
  21. Junio C HamanoSep 2, 2012

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.