From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Cc: Jesper Juhl <jesper.juhl@gmail.com>, Victor Hugo <victor@vhugo.net>
Subject: LKML FAQ, newsgroups and newbies (was Re: [RFC] e-mail clients)
Date: Fri, 08 Sep 2006 22:03:48 +0200 [thread overview]
Message-ID: <4501CCA4.1000100@flower.upol.cz> (raw)
In-Reply-To: <9a8748490609080124q5b32d325l1c251d3e2d800f1d@mail.gmail.com>
Jesper Juhl wrote:
> On 08/09/06, Victor Hugo <victor@vhugo.net> wrote:
>> about which client to use on lkml?? Pine?? Mutt??
>> Thunderbird?? Telnet??
>>
> I personally use both 'pine' and 'kmail' and they both work perfectly
> for sending patches.
>
Why NNTP was abandoned and development switched to pure SMTP+maillist ?
Pros and cons are. Classic NNTP consider "courtesy copies" (Cc) to be impolite,
pure SMTP eases scripting of handling patches. But, adding CCs to NNTP postings
is possible, while reading big volumes is very convenient. Any backend SMTP
MUA/MTA may be used for patch-handling job. Discussion about (any web-based)
bugzilla vs e-mail, applies to NNTP: there are many readers (with e-mail
support as well), easy managing, ASCII.
IMHO it's very good start for anyone. Thus i've found a way to step into
development even i'm not cs, guru, hacker, just unix-like os (stupid) user,
even have had read all that treating discussions about lkml volumes.
I use Mozilla-newsreader-gmane.org + SMTP MTA | mutt MUA, but couldn't yet
develop patch handling, i didn't write a good one yet.
So things like:
* press articles' questions "It's so many messages in LKML, how one can read
them all ???",
* SMTP@spam (key is _@_ ;),
* e-mail handling headache,
is prize for not using NNTP as a primary. I really want to see reasonable
explanations on question above. FAQ has "COLA = comp.os.linux.announce
(newsgroup)", nothing more about NNTP as it used to be used.
-*- OT -*-
On every LKML post there's a message about FAQ URL, that page has
"NOTE: this page is no longer maintained..." (Dot coms boomed) Many
linux-related sites also outdated. Advogato is going down (well most of linux
developers moved from it years ago), we are getting older, having families,
children, something becomes more/less important. So that's next ? (hopefully
not an accelerated kernel-XML-Parser 4 Desktop Linux (R) ;)
Maybe linux-kernel need new blood ? Victor Hugo, being not from
linux-visionaries, you're welcome.
--
-o--=O`C /. .\ (i want ..., but with ENOPATCH) (+)
#oo'L O o |
<___=E M ^-- | (you're ... the wrong ...)
next prev parent reply other threads:[~2006-09-08 19:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 0:02 [RFC] e-mail clients Victor Hugo
2006-09-08 7:13 ` Jan Engelhardt
2006-09-08 7:24 ` Michal Piotrowski
2006-09-08 8:17 ` Jan Engelhardt
2006-09-08 8:31 ` Michal Piotrowski
2006-09-08 9:05 ` Jan Engelhardt
2006-09-08 22:54 ` Pavel Machek
2006-09-08 8:24 ` Jesper Juhl
2006-09-08 10:29 ` Rafael J. Wysocki
2006-09-08 12:54 ` Hans-Peter Jansen
2006-09-08 13:18 ` Gene Heskett
2006-09-08 16:04 ` Vadim Lobanov
2006-09-08 16:06 ` Ondrej Zary
2006-09-08 14:05 ` Alistair John Strachan
2006-09-08 20:03 ` Oleg Verych [this message]
2006-09-08 8:47 ` Paolo Ornati
2006-09-08 10:54 ` Stefan Richter
2006-09-08 14:53 ` Brice Goglin
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=4501CCA4.1000100@flower.upol.cz \
--to=olecom@flower.upol.cz \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=victor@vhugo.net \
/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