From: Karl O. Pinc <kop@meme.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] The way the list manages patch submission
Date: Fri, 03 Aug 2012 16:12:28 -0500 [thread overview]
Message-ID: <1344028348.3155.4@mofo> (raw)
In-Reply-To: <CAHgS8JVrBVQv-1y+24dmqYFwsezDZvUACDfJeVm5jWE78k0OSw@mail.gmail.com> (from andywyse6@gmail.com on Fri Aug 3 15:43:50 2012)
On 08/03/2012 03:43:50 PM, 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.
It seems only to affect patches sent to the list, not regular
emails like this one. I don't think it has to do with the
client. git send-email --compose sent a patch and a message
and I got the message back on the list but not the patch.
> I see several patches from you over recent days, including the
> re-submissions, so my guess is the same is happening to you.
Cool. Thanks for the ack.
Karl <kop@meme.com>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
next prev parent reply other threads:[~2012-08-03 21:12 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 [this message]
2012-08-03 21:45 ` Graeme Russ
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=1344028348.3155.4@mofo \
--to=kop@meme.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.