From: Graeme Russ <graeme.russ@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] The way the list manages patch submission
Date: Sat, 04 Aug 2012 07:45:22 +1000 [thread overview]
Message-ID: <501C4672.7060003@gmail.com> (raw)
In-Reply-To: <CAHgS8JVrBVQv-1y+24dmqYFwsezDZvUACDfJeVm5jWE78k0OSw@mail.gmail.com>
Hi Karl & Andy,
On 08/04/2012 06:43 AM, Andy Sharp wrote:
> I think it's a matter of the list software isn't sending emails to the
> original sender, regardless of the setting for that user. The same
> happened to me with a patch set I sent on Wednesday. They all went to the
> list, based on looking in the online archive, even though I never got those
If you see your email in the archive and/or patchwork (note only patches
and comments on patches will make it into patchwork - also that Patchwork
will drop patches containing 'funny (non-ASCII)' characters) then the list
is processing it correctly.
We are currently looking into a home-brew patchwork replacement to augment
how we process patches via the mailing list. Comments are appreciated:
http://www.denx.de/wiki/view/U-Boot/ToolsPatchTracking
> emails in my own mailbox. I also got a couple of weird bounces ...
> something about it being a moderated list for about half of the six emails.
> Weird.
emails over, I think, about 100kB need approval before being forwarded to
the list. Wolfgang, since these appear to be rather rare, can this limit be
dropped, at least for a little while to test the impact?
> I see several patches from you over recent days, including the
> re-submissions, so my guess is the same is happening to you.
So do I - big thanks for the documentation updates, they all too often get
overlooked.
Regards,
Graeme
>
> Cheers,
>
> a
>
>
> On Fri, Aug 3, 2012 at 11:26 AM, Karl O. Pinc <kop@meme.com> wrote:
>
>> Hi,
>>
>> As a beginner here I have to say it's really
>> surprising the way the list disappears patches
>> sent to the list. Usually when you send an email
>> you expect it to be delivered.
>>
>> I'm sure you have your reasons for this behavior
>> but I thought I'd comment anyway.
>>
>> As a suggestion, if the patch won't go to the list
>> for comment perhaps there's a way to send an
>> ack back to the sender to let them know what
>> will happen next?
>>
>> Regards,
>>
>> Karl <kop@meme.com>
>> Free Software: "You don't pay back, you pay forward."
>> -- Robert A. Heinlein
>>
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>>
>
>
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
next prev parent reply other threads:[~2012-08-03 21:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 18:26 [U-Boot] The way the list manages patch submission Karl O. Pinc
2012-08-03 20:43 ` Andy Sharp
2012-08-03 21:12 ` Karl O. Pinc
2012-08-03 21:45 ` Graeme Russ [this message]
2012-08-03 22:46 ` Wolfgang Denk
2012-08-04 0:56 ` Karl O. Pinc
2012-08-04 13:35 ` Wolfgang Denk
2012-08-04 16:55 ` Karl O. Pinc
2012-08-04 23:08 ` Wolfgang Denk
2012-08-05 9:15 ` Alexander Holler
2012-08-04 16:58 ` Karl O. Pinc
2012-08-04 17:00 ` Karl O. Pinc
-- strict thread matches above, loose matches on Subject: below --
2012-08-04 13:37 Wolfgang Denk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=501C4672.7060003@gmail.com \
--to=graeme.russ@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.