public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] The way the list manages patch submission
Date: Sat, 04 Aug 2012 15:35:49 +0200	[thread overview]
Message-ID: <20120804133550.0107920022C@gemini.denx.de> (raw)
In-Reply-To: <1344041771.12337.2@mofo>

Dear Karl,

In message <1344041771.12337.2@mofo> you wrote:
>
> The trouble is getting a patch message back from the list when you
> send a patch in.  For example I sent

Why would you want to get your own messages back?  You already know
what you sent, don't you?   

> <1344017124-5749-1-git-send-email-kop@meme.com>
> [PATCH v2] README: Add handy kermit primer

Yes, and as you can see for example from the list archive at gmane
that has been properly deliverd; also your V2 of it:

08/03 "Karl O. Pinc"     [U-Boot] [PATCH] README: Add handy kermit primer
http://article.gmane.org/gmane.comp.boot-loaders.u-boot/136913

08/03 "Karl O. Pinc"     [U-Boot] [PATCH v2] README: Add handy kermit primer
http://article.gmane.org/gmane.comp.boot-loaders.u-boot/136919

> The mail logs show the message going out, but nothing
> ever comes back with that message id.

Why should it?

> Perhaps it's because git send-email automatically cc-s me,
> so the list decides not to send the patch back?
> I've added myself as a cc to this message to see
> if that matters.

Your registration in the mailing list has the "nodupes" flag set,
which is documented as:

	Avoid duplicate copies of messages?

	When you are listed explicitly in the To: or Cc: headers of a
	list message, you can opt to not receive another copy from the
	mailing list. Select Yes to avoid receiving copies from the
	mailing list; select No to receive copies.

	If the list has member personalized messages enabled, and you
	elect to receive copies, every copy will have a
	X-Mailman-Copy: yes header added to it. 

You selected that you don't want dupes, so you should not complain
that you don't get dupes.

> In any case it's not a big deal.  It's just, odd.

It is the configuration you selected. If you don't like it, then go
to the list page, click on "edit options", and change your settings.
Most people prefer it tis way, though.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
When all is said and done, more is said than done.

  reply	other threads:[~2012-08-04 13:35 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
2012-08-03 22:46     ` Wolfgang Denk
2012-08-04  0:56       ` Karl O. Pinc
2012-08-04 13:35         ` Wolfgang Denk [this message]
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=20120804133550.0107920022C@gemini.denx.de \
    --to=wd@denx.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox