Eric Wong writes:
> I don't think postfix, SpamAssassin, or dovecot strip that..
> ...
> I would expect the blank context lines in the QP version to have
> "=20". I sent this to t...@public-inbox.org using
> `git send-email --transfer-encoding=quoted-printable' and it
> confirms the blank contex
René Scharfe writes:
> Am 22.08.22 um 06:06 schrieb Junio C Hamano:
>> René, do you remember if you used diff.suppressBlankEmpty
>> configuration when generating the patch in question at:
>>
>>
>> https://public-inbox.org/git/6727daf1-f077-7319-187e-ab4e55d
Junio C Hamano writes:
>> So, I'm wondering if the search indexing code of public-inbox
>> should s/^$/ /mgs before feeding stuff to `git patch-id'; and/or
>> if `git patch-id' should be assuming empty lines and lines with a
>> single SP are the same...
Eric Wong writes:
> While poking around at the newish patchid indexing support in
> public-inbox[1], I noticed an inconsistency in how it seems to
> mishandle quoted-printable messages.
> ...
> So, I'm wondering if the search indexing code of public-inbox
> should s/^$/ /mgs before feeding stuff
Eric Wong writes:
> Samuel Lijin wrote:
>> Sorry, should've been clearer - I did check my spambox in my original
>> message. Some old patches from Brandon were in there, but the ones I
>> mentioned in my original message just seem to have been dropped.
>
> Apparently, vger also throttles mail to
Arif Khokar writes:
> One concern I have regarding this idea is whether or not SMTP servers
> typically replace a Message-Id header set by the client.
The clients are supposed to give Message-IDs, but because some
clients fail to do so, SMTP server implementations are allowed to
add an ID to avo
Arif Khokar writes:
> ... I
> still think it would be better to be able to list the message-id
> values in the header or body of the cover letter message of a patch
> series (preferably the former) in order to facilitate downloading the
> patches via NNTP from gmane or public-inbox.org.
You are
Santiago Torres writes:
<>???
Eric, I've noticed that this message
http://public-inbox.org/git/20170118182831.pkhqu2np3bh2puei@LykOS.localdomain/
and all messages from Santiago appear empty when they come via
public-inbox.org; the reason I suspect we haven't heard much
complaints is because
Eric Wong writes:
> I see a choice of mail client as no different than a choice of
> text editor. Neither my mail client or text editor is heavily
> customized. The key feature I rely on from both tools is piping
> data to external commands.
FWIW, that applies to me exactly, too.
> unsubscrib
Jeff King writes:
> For my workflow, it is not about "initial skip", but rather just "skip
> emails that don't have patches in them at all".
OK. That is different from "the subject line says 0/N so let's
skip".
If we can safely determine that there is no patch in a message,
skipping it may fee
Stefan Beller writes:
> In your work flow, how do you respect the cover letter?
> e.g. in 3787e3c16ced:
>
> Merge branch 'ew/http-backend-batch-headers'
>
> The http-backend (the server-side component of smart-http
> transport) used to trickle the HTTP header one at a time. Now
>
Stefan Beller writes:
> So as a discussion starter:
> * Should git am skip a patch 00/XX automatically ?
No. My preference is to add "--initial-skip=", though.
When I receive a patch series to reroll another series, I somehow
know and verify that earlier N patches have not changed, I detach
th
12 matches
Mail list logo
