list etiquette

list etiquette

[Tobin Harding]

LKML list etiquette question.

When asking a [simple] question that receives an suitable answer is it correct
etiquette to reply with a thank you email or is this just adding noise to the
list?

thanks,
Tobin.

list etiquette

[Robert P. J. Day]

On Mon, 6 Jun 2016, Tobin Harding wrote:

> LKML list etiquette question.
>
> When asking a [simple] question that receives an suitable answer is
> it correct etiquette to reply with a thank you email or is this just
> adding noise to the list?

  i would just let it go, unless you have something you want to add,
or possibly a summary that would be useful for future readers.

rday

p.s. conversely, if you're *answering* someone's question, take the
time to really flesh it out so it's as useful as possible to as many
people as possible.

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

list etiquette

[Anuz Pratap Singh Tomar]

On Mon, Jun 6, 2016 at 9:53 AM, Tobin Harding <me@tobin.cc> wrote:

> LKML list etiquette question.
>
> When asking a [simple] question that receives an suitable answer is it
> correct
> etiquette to reply with a thank you email or is this just adding noise to
> the
> list?
>
> Generally, it is understood.
Here are some mailing list for guidelines which might be relevant

http://kernelnewbies.org/mailinglistguidelines


> thanks,
> Tobin.
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>



-- 
Thank you
Warm Regards
Anuz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160606/b45b289b/attachment.html 

list etiquette

[Frank Ch. Eigler]

me at tobin.cc wrote:

> LKML list etiquette question.  When asking a [simple] question that
> receives an suitable answer is it correct etiquette to reply with a
> thank you email or is this just adding noise to the list?

(Probably obvious, but you can always reply with a "thank you",
sent directly to the people who answered rather than to the list.)

- FChE

list etiquette

[Tobin Harding]

On Tue, Jun 07, 2016 at 12:03:57PM -0400, Frank Ch. Eigler wrote:
> 
> me at tobin.cc wrote:
> 
> > LKML list etiquette question.  When asking a [simple] question that
> > receives an suitable answer is it correct etiquette to reply with a
> > thank you email or is this just adding noise to the list?
> 
> (Probably obvious, but you can always reply with a "thank you",
> sent directly to the people who answered rather than to the list.)

I had got the vibe that it was unacceptable to mail people directly and not cc
the list. Is this response correct that there are times it is acceptable to
exclude the list. GregKH has had to nudge me twice for doing this so I am very
hesitant to write any emails that are not in the clear (cc'ing a list).

Tobin

list etiquette

[Anuz Pratap Singh Tomar]

I don't think greg or any senior kernel developer would like to get
personal mail, which are officially the list/community business.
Skipping thank you mails is really okay. you can always thank them in
advance is a good idea.

On Sat, Jun 11, 2016 at 11:47 AM, Tobin Harding <me@tobin.cc> wrote:

> On Tue, Jun 07, 2016 at 12:03:57PM -0400, Frank Ch. Eigler wrote:
> >
> > me at tobin.cc wrote:
> >
> > > LKML list etiquette question.  When asking a [simple] question that
> > > receives an suitable answer is it correct etiquette to reply with a
> > > thank you email or is this just adding noise to the list?
> >
> > (Probably obvious, but you can always reply with a "thank you",
> > sent directly to the people who answered rather than to the list.)
>
> I had got the vibe that it was unacceptable to mail people directly and
> not cc
> the list. Is this response correct that there are times it is acceptable to
> exclude the list. GregKH has had to nudge me twice for doing this so I am
> very
> hesitant to write any emails that are not in the clear (cc'ing a list).
>
> Tobin
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>



-- 
Thank you
Warm Regards
Anuz
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160611/8b63c2e3/attachment.html 

list etiquette

[Manavendra Nath Manav]

I think you should focus more on kernel development/discussion rather
than saying thank you's. Etiquette wise it's perfectly okay.

On 6/11/16, Anuz Pratap Singh Tomar <chambilkethakur@gmail.com> wrote:
> I don't think greg or any senior kernel developer would like to get
> personal mail, which are officially the list/community business.
> Skipping thank you mails is really okay. you can always thank them in
> advance is a good idea.
>
> On Sat, Jun 11, 2016 at 11:47 AM, Tobin Harding <me@tobin.cc> wrote:
>
>> On Tue, Jun 07, 2016 at 12:03:57PM -0400, Frank Ch. Eigler wrote:
>> >
>> > me at tobin.cc wrote:
>> >
>> > > LKML list etiquette question.  When asking a [simple] question that
>> > > receives an suitable answer is it correct etiquette to reply with a
>> > > thank you email or is this just adding noise to the list?
>> >
>> > (Probably obvious, but you can always reply with a "thank you",
>> > sent directly to the people who answered rather than to the list.)
>>
>> I had got the vibe that it was unacceptable to mail people directly and
>> not cc
>> the list. Is this response correct that there are times it is acceptable
>> to
>> exclude the list. GregKH has had to nudge me twice for doing this so I am
>> very
>> hesitant to write any emails that are not in the clear (cc'ing a list).
>>
>> Tobin
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>>
>
>
>
> --
> Thank you
> Warm Regards
> Anuz
>


-- 
Manavendra Nath Manav

list etiquette

[mhornung.linux at gmail.com]

Hi Tobin,

On Mon, 06. Jun 18:53, Tobin Harding wrote:
> LKML list etiquette question.
> 
> When asking a [simple] question that receives an suitable answer is it correct
> etiquette to reply with a thank you email or is this just adding noise to the
> list?

Someone reading your question (and the suitable answer) later on might wonder
if the answer was correct or not. So yes, it is always useful to reply with a
"thank you" if the answer was correct and useful.

> 
> thanks,
> Tobin.

With best regards

Michael
> 
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

list etiquette

[Carlo Caione]

On Tue, Jun 7, 2016 at 7:40 PM,  <mhornung.linux@gmail.com> wrote:
> Hi Tobin,
>
> On Mon, 06. Jun 18:53, Tobin Harding wrote:
>> LKML list etiquette question.
>>
>> When asking a [simple] question that receives an suitable answer is it correct
>> etiquette to reply with a thank you email or is this just adding noise to the
>> list?
>
> Someone reading your question (and the suitable answer) later on might wonder
> if the answer was correct or not. So yes, it is always useful to reply with a
> "thank you" if the answer was correct and useful.

This generates useless spam and traffic in a ml that already counts
hundreds of mails per day.

-- 
Carlo Caione

List etiquette

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 270 bytes --]

Hi all,

Just a short note to mention a couple of things:

	- please do *not* post html formatted emails.  I may start just
rejecting them soon.

	- please cut down the quoting in replies to what is needed for
context.

Thanks
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

List etiquette

[David Antliff]

[-- Attachment #1: Type: text/plain, Size: 594 bytes --]

Hello,

I'm a new subscriber to this list and looking to ask a specific question
shortly. However I would like to bring two things up based on this page:

https://ozlabs.org/mailman/listinfo/linuxppc-embedded

1. The list rules and posting guidelines URLs are out of service:

 - http://lists.linuxppc.org/rules.html
 - http://lists.linuxppc.org/guidelines.html

2. There is a recommendation to look for answers to questions in the
list archives. There does not seem to be any way to search these, except
with Google site: syntax. Am I missing something here?

Regards,
David

[-- Attachment #2: Type: text/html, Size: 1207 bytes --]

List etiquette.

[David Woodhouse]

I've recently found myself having to inspect and reject a lot of crap
which the list filters have caught, so it's time to rant about it a
little... :)

Please read http://www.infradead.org/~dwmw2/email.html

In particular, please ensure that you use a sensible mail reader which
inserts References: and/or In-Reply-To: headers such that threading
works correctly. Please ensure that you do not try to start a new thread
by just replying to an existing list message and changing the subject,
for similar reasons. And don't send HTML.


-- 
dwmw2

Re: List etiquette.

[David Woodhouse]

On Wed, 2003-04-23 at 10:15, David Woodhouse wrote:
> I've recently found myself having to inspect and reject a lot of crap
> which the list filters have caught, so it's time to rant about it a
> little... :)
> 
> Please read http://www.infradead.org/~dwmw2/email.html
> 
> In particular, please ensure that you use a sensible mail reader which
> inserts References: and/or In-Reply-To: headers such that threading
> works correctly. Please ensure that you do not try to start a new thread
> by just replying to an existing list message and changing the subject,
> for similar reasons. And don't send HTML.

... and don't send stupid unenforceable disclaimers which achieve
nothing but to show the world how clueless your company legal department
is, and don't top-post, and don't set up broken autoresponders which
reply to anywhere other than the SMTP reverse-path.


-- 
dwmw2

Re: List etiquette.

[Jörn Engel]

On Wed, 23 April 2003 10:15:56 +0100, David Woodhouse wrote:
>
> Please ensure that you do not try to start a new thread
> by just replying to an existing list message and changing the subject,
> for similar reasons.

Why exactly? I kind of like the habit of changing the subject in the
middle of a thread where appropriate, like "foo (was: bar)".

You are the boss, but I'd like to know the rationale.

Jörn

-- 
Eighty percent of success is showing up.
-- Woody Allen

Re: List etiquette.

[Russ Dill]

On Wed, 2003-04-23 at 13:40, Jörn Engel wrote:
> On Wed, 23 April 2003 10:15:56 +0100, David Woodhouse wrote:
> >
> > Please ensure that you do not try to start a new thread
> > by just replying to an existing list message and changing the subject,
> > for similar reasons.
> 
> Why exactly? I kind of like the habit of changing the subject in the
> middle of a thread where appropriate, like "foo (was: bar)".

He doesn't mean a topic change like, "There is a bug in tool foo blah
blah blah" "I like that tool, but I use tool bar blah blah blah" "(New
subject) did you know how to do x in tool bar?"

He means "I have an oops when I use foo with bar" "(reply) Where can I
find the latest CVS snapshot?"

Lazy people, not sensible topic shifting

Re: List etiquette.

[Jörn Engel]

On Wed, 23 April 2003 13:51:05 -0700, Russ Dill wrote:
> 
> On Wed, 2003-04-23 at 13:40, Jörn Engel wrote:
> > 
> > Why exactly? I kind of like the habit of changing the subject in the
> > middle of a thread where appropriate, like "foo (was: bar)".
> 
> He doesn't mean a topic change like, "There is a bug in tool foo blah
> blah blah" "I like that tool, but I use tool bar blah blah blah" "(New
> subject) did you know how to do x in tool bar?"
> 
> He means "I have an oops when I use foo with bar" "(reply) Where can I
> find the latest CVS snapshot?"

Well, my NOSPAM SH*T rant ended up in the spam folder until David
manually accepted it. So my best gues of what he means is "don't do
anything that creates work for me". And since the spam filter rules
are the way they are,...

But I don't want to second-guess what other people really meant.

Jörn

-- 
With a PC, I always felt limited by the software available. On Unix, 
I am limited only by my knowledge.
-- Peter J. Schoenster

Re: List etiquette.

[Grant Edwards]

On Wed, Apr 23, 2003 at 10:40:37PM +0200, Jörn Engel wrote:
> On Wed, 23 April 2003 10:15:56 +0100, David Woodhouse wrote:
> >
> > Please ensure that you do not try to start a new thread
> > by just replying to an existing list message and changing the subject,
> > for similar reasons.
> 
> Why exactly? I kind of like the habit of changing the subject in the
> middle of a thread where appropriate, like "foo (was: bar)".
> 
> You are the boss, but I'd like to know the rationale.

If you don't change the In-Reply-To: header, a decent MUA will
thread the new article with the old thread.  It doesn't belong
there (or you wouldn't have changed the topic).

If you want to reply to a message and start a new thread, make
sure you remove the In-Reply-To: header also.  That way you'll
be starting a new thread -- which one must presume is your
intention when you change the Subject: header.

-- 
Grant Edwards
grante@visi.com

Re: List etiquette.

[Jörn Engel]

On Thu, 24 April 2003 09:47:09 -0500, Grant Edwards wrote:
> 
> If you don't change the In-Reply-To: header, a decent MUA will
> thread the new article with the old thread.  It doesn't belong
> there (or you wouldn't have changed the topic).

Well, if I didn't want the reference to the old thread, I wouldn't
reply in the first place. The subject has shifted already, the subject
header simply makes this clear for everyone who might want to ignore
that sub-thread now. But as long as I quote from the original thread,
I personally think that it should remain in it.

Opinions vary, though.

> If you want to reply to a message and start a new thread, make
> sure you remove the In-Reply-To: header also.

And references.

Yes, sometimes it makes sense to start a new thread, for psychological
reasons. But usually the subject of the mail contents doesn't fit the
subject anymore and the author simply let's other people know before
they have to read it.

Anyway, I will just keep the Re: and think twice. :)

Jörn

-- 
Correctness comes second.
Features come third.
Performance comes last.
Maintainability is needed for all of them.