From: Oleg Verych <olecom@flower.upol.cz>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>, Krzysztof Halasa <khc@pm.waw.pl>,
Medve Emilian-EMMEDVE1 <Emilian.Medve@freescale.com>,
Helge Deller <deller@gmx.de>
Subject: About summary in the subject (Re: [PATCH 0/2] Colored kernel output (run2))
Date: Sat, 6 Oct 2007 23:55:27 +0200 [thread overview]
Message-ID: <20071006215527.GI22435@flower.upol.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0710062300200.30354@fbirervta.pbzchgretzou.qr>
On Sat, Oct 06, 2007 at 11:03:38PM +0200, Jan Engelhardt wrote:
>
> On Oct 6 2007 23:03, Oleg Verych wrote:
> >>
> >> (btw., i corrected the subject line to remove the 'NAK'. Why do you
> >> think you can 'NAK' a patch in this field?)
> >
> >I added comment (like this), so anyone can skip reading body, if headers
> >are "Oleg Verych && NAK". In case if `NAK' have a magic meaning in the
> >LKML, like control characters in the tty, i'm sorry.
> >
> >But how to express opinion quickly and easily?
>
> You can't. I think that people will usually be interested _why_ you
> voted for or against something
Do you really think so? Yes, there are possibly LKML bots, that will
read all messages in every thread. But i doubt they are humans.
I also think, that kill-files and kill-names are common tools of the LKML
readers. Thus, if someone sees my name with something like NAK in the
subject, then nothing to worry about: next, please. I just amazed how
inefficiently Subject, To, Cc headers are used. Everybody hurry through
huge mail backlogs with subjects in thread all like one.
Summary and keywords headers are not used, so why not to make
greping/selecting interesting/useful messages more efficient (and not
only for those who is in Cc list)?
Every mail/news reader displays To and Subject, so latter is last hope of
increasing of efficiency, even in small threads.
> (given the number of vote-submitters does not go through the roof).
> That clearly won't fit into the subject,
Sorry, i cannot see, what you are trying to say here. To place all
acks-by to subject? No, just to get summary in one particular reply.
> and even if RFC822 allowed it, it's only displayed like 40 chars wide.
> The submitter (me in this case) will even look at *all* mails, so as to
> (1) address the NAKs and (2) address the hidden feature requests in
> ACKs. :-)
____
next prev parent reply other threads:[~2007-10-06 21:41 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0710062005190.5969@fbirervta.pbzchgretzou.qr>
2007-10-06 19:13 ` [PATCH 1/2] Colored kernel output (run2) Jan Engelhardt
2007-10-08 13:28 ` Denys Vlasenko
2007-10-06 19:13 ` [PATCH 2/2] " Jan Engelhardt
[not found] ` <20071006195105.GE22435@flower.upol.cz>
[not found] ` <20071006194820.GA30579@elte.hu>
2007-10-06 21:03 ` [PATCH 0/2] " Oleg Verych
2007-10-06 21:03 ` Jan Engelhardt
2007-10-06 21:55 ` Oleg Verych [this message]
2007-10-07 6:07 ` Ingo Molnar
2007-10-07 11:10 ` "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage" Oleg Verych
2007-10-07 14:15 ` NAK nettiquete (was Re: "Re: [PATCH 0/2] Colored kernel output (run2)" Valdis.Kletnieks
2007-10-07 15:12 ` Alan Cox
2007-10-07 15:29 ` Jan Engelhardt
2007-10-07 16:23 ` Alan Cox
2007-10-07 23:09 ` Jan Engelhardt
2007-10-07 15:46 ` Valdis.Kletnieks
2007-10-07 18:11 ` NAK nettiquete (was " Arnaldo Carvalho de Melo
2007-10-07 16:12 ` "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage" Ingo Molnar
2007-10-07 18:47 ` Rene Herman
2007-10-07 18:58 ` Jan Engelhardt
2007-10-07 19:27 ` Rene Herman
2007-10-07 20:02 ` Jan Engelhardt
2007-10-07 19:13 ` Willy Tarreau
2007-10-07 19:47 ` Oleg Verych
2007-10-07 21:23 ` Ingo Molnar
2007-10-07 21:38 ` Alan Cox
2007-10-12 13:42 ` Bill Davidsen
2007-10-08 3:23 ` Willy Tarreau
2007-10-08 19:27 ` initramfs: coloring in userspace, "[PATCH 0/2] Colored kernel output (run2)" Oleg Verych
2007-10-07 19:53 ` "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage" Rene Herman
2007-10-07 19:56 ` Jan Engelhardt
2007-10-07 20:00 ` Rene Herman
2007-10-07 20:04 ` Jan Engelhardt
2007-10-07 20:06 ` Rene Herman
2007-10-07 20:50 ` tty UI (Re: [PATCH 0/2] Colored kernel output (run2)) Oleg Verych
2007-10-07 20:43 ` Jan Engelhardt
2007-10-07 22:18 ` syntax highlighting, emacs ([PATCH " Oleg Verych
2007-10-07 22:11 ` Jan Engelhardt
2007-10-08 0:29 ` Ken Moffat
2007-10-08 3:29 ` "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage" Willy Tarreau
2007-10-07 21:11 ` Ingo Molnar
2007-10-07 23:02 ` Oleg Verych
2007-10-07 23:01 ` Jan Engelhardt
2007-10-07 23:33 ` Oleg Verych
2007-10-07 22:40 ` Alistair John Strachan
2007-10-07 23:10 ` Rene Herman
2007-10-07 23:20 ` Alistair John Strachan
2007-10-07 23:33 ` Alistair John Strachan
2007-10-07 23:15 ` Alan Cox
2007-10-07 16:37 ` Jan Engelhardt
2007-10-12 13:16 ` Bill Davidsen
2007-10-12 14:57 ` Oleg Verych
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=20071006215527.GI22435@flower.upol.cz \
--to=olecom@flower.upol.cz \
--cc=Emilian.Medve@freescale.com \
--cc=davej@redhat.com \
--cc=deller@gmx.de \
--cc=jengelh@computergmbh.de \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®