From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: New SCM and commit list
Date: Mon, 11 Apr 2005 09:10:20 +1000 [thread overview]
Message-ID: <1113174621.9517.509.camel@gaston> (raw)
Hi Linus !
Do you intend to continue posting "commited" patches to a mailing list
like bk scripts did to bk-commits-head@vger ? As I said a while ago, I
find this very useful, especially with the actual patch included in the
commit message (which isn't the case with most other projects CVS commit
lists, and I find that annoying).
If yes, then I would appreciate if you could either keep the same list,
or if you want to change the list name, keep the subscriber list so
those of us who actually archive it don't miss anything ;)
Thanks !
Regards,
Ben.
next reply other threads:[~2005-04-10 23:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 23:10 Benjamin Herrenschmidt [this message]
2005-04-10 23:26 ` New SCM and commit list Linus Torvalds
2005-04-11 3:25 ` James Bottomley
2005-04-11 20:53 ` Greg KH
2005-04-11 21:26 ` Linus Torvalds
2005-04-11 21:31 ` James Bottomley
2005-04-12 4:24 ` Arjan van de Ven
2005-04-13 20:04 ` H. Peter Anvin
2005-04-11 5:53 ` Jeff Garzik
2005-04-11 6:15 ` Linus Torvalds
2005-04-11 6:40 ` Ryan Anderson
2005-04-11 6:47 ` Geert Uytterhoeven
2005-04-11 7:38 ` Ingo Molnar
2005-04-11 12:51 ` Chris Mason
2005-04-11 19:32 ` Chris Mason
2005-04-11 22:50 ` Daniel Barkalow
2005-04-12 8:36 ` Geert Uytterhoeven
2005-04-12 9:52 ` Catalin Marinas
2005-04-16 8:35 ` Paul Jackson
2005-04-18 8:18 ` Catalin Marinas
2005-04-11 7:13 ` David Woodhouse
-- strict thread matches above, loose matches on Subject: below --
2005-04-11 18:18 Adam J. Richter
2005-04-12 3:02 Adam J. Richter
2005-04-12 21:54 ` Daniel Barkalow
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=1113174621.9517.509.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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