Am 04.08.2012 18:55, schrieb Karl O. Pinc:
So perhaps the u-boot list default that has
duplicate elimination turned on,
where other lists do not, is factor contributing
to the confusion. I've never had
Some mail-servers have that feature enabled by default too. E.g.
cyrus-imapd (called
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?
Dear Karl,
I wrote:
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.
While you are at it, check if you want to enable the Receive your own
posts to the list? as
Dear Wolfgang,
On 08/04/2012 08:35:49 AM, Wolfgang Denk wrote:
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
On 08/04/2012 08:35:49 AM, Wolfgang Denk wrote:
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
On 08/04/2012 11:58:23 AM, Karl O. Pinc wrote:
FYI. I got the above message twice. Probably because you
sent the message To: me and Cc:-ed the list instead of
sending the message To: the list and cc:-ing me.
No. I am wrong. I was confused. :-P
Sorry.
Karl k...@meme.com
Free
Dear Karl,
In message 1344099312.12337.4@mofo you wrote:
the patch was not.) No getting around the moderation
delay, just thought I'd mention it. Perhaps you could
alter the list welcome message to note that the
list is moderated. This won't help; nobody
reads the instructions. :/ But
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
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
emails
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
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
Dear Graeme Russ,
In message 501c4672.7060...@gmail.com you wrote:
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 no reason
On 08/03/2012 05:46:56 PM, Wolfgang Denk wrote:
I have no diea why there are two people (Karl and Any) appear to have
problems with list delivery - I cannot see any such problems. As far
as I can tell, all their messages have been properly delivered to the
list and the archives. I tend to
13 matches
Mail list logo
