Linux PARISC architecture development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: deller@gmx.de, torvalds@linux-foundation.org,
	linux-parisc@vger.kernel.org
Subject: Re: parisc tree maintainer
Date: Mon, 06 Dec 2010 15:53:11 -0600	[thread overview]
Message-ID: <1291672391.7021.33.camel@mulgrave.site> (raw)
In-Reply-To: <20101206164310.GQ25668@bombadil.infradead.org>

On Mon, 2010-12-06 at 11:43 -0500, Kyle McMartin wrote:
> I'm getting a bit bored of maintaining the parisc trees and such... Do
> either of you want to take over? If you do, please reply so that Linus
> knows that the next pull request will come from you instead of me.

I suppose I can ... it's not a high volume tree, fortunately.  Thanks
for doing it this long ... although I've got to say, I think continuing
would be good practise for you.

James



  parent reply	other threads:[~2010-12-06 21:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06 16:43 parisc tree maintainer Kyle McMartin
2010-12-06 18:30 ` John David Anglin
2010-12-06 21:53 ` James Bottomley [this message]
2010-12-06 22:26   ` Helge Deller
2011-01-15 18:32     ` Domenico Andreoli

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=1291672391.7021.33.camel@mulgrave.site \
    --to=james.bottomley@hansenpartnership.com \
    --cc=deller@gmx.de \
    --cc=kyle@mcmartin.ca \
    --cc=linux-parisc@vger.kernel.org \
    --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