git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	Kyle Moffett <mrmacman_g4@mac.com>,
	Salikh Zakirov <salikh@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	LKML Kernel <linux-kernel@vger.kernel.org>,
	Joe Perches <joe@perches.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-pm@lists.linux-foundation.org, git@vger.kernel.org
Subject: Re: [linux-pm] Re: Storing Maintainers info around the kernel tree
Date: Fri, 17 Aug 2007 03:43:51 +0200	[thread overview]
Message-ID: <46C4FD57.3000101@gmail.com> (raw)
In-Reply-To: <46C4C40C.4050406@s5r6.in-berlin.de>

On 08/16/2007 11:39 PM, Stefan Richter wrote:
> Rene Herman wrote:

>> I personally don't think there's a whole lot wrong with more and more
>> expecting people who submit patches (for whom this automation is
>> intended) to be using git.
> 
> You mean "people who frequently submit patches for various different
> subsystems".

Erm, I guess. Is that agreeing or disagreeing with me?

Rene.

  reply	other threads:[~2007-08-17  1:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46bffbd3.IqsNHrHU1Y9BF7Dd%joe@perches.com>
     [not found] ` <20070814232430.GA9325@redhat.com>
     [not found]   ` <2ABEF126-D860-46D2-8E15-673C3ADB51A0@mac.com>
     [not found]     ` <200708151321.05959.rjw@sisk.pl>
2007-08-16 13:04       ` Storing Maintainers info around the kernel tree Kyle Moffett
2007-08-16 15:13         ` Rene Herman
2007-08-16 15:31           ` [linux-pm] " Alan Stern
2007-08-16 15:50             ` Rene Herman
2007-08-16 21:39               ` Stefan Richter
2007-08-17  1:43                 ` Rene Herman [this message]
2007-08-17  1:58                   ` Alan Stern
2007-08-17  2:18                     ` Rene Herman
2007-08-17  6:25                       ` Stefan Richter

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=46C4FD57.3000101@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mrmacman_g4@mac.com \
    --cc=salikh@gmail.com \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=stern@rowland.harvard.edu \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).