From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH] Add myself (Bob Peterson) as a maintainer of GFS2
Date: Tue, 17 Feb 2015 16:06:44 -0500 (EST) [thread overview]
Message-ID: <2095172778.14833591.1424207204509.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20150217013408.6025d2f9@canb.auug.org.au>
----- Original Message -----
> Hi Bob,
>
> On Mon, 16 Feb 2015 09:20:56 -0500 (EST) Bob Peterson <rpeterso@redhat.com>
> wrote:
> >
> > This patch adds Bob Peterson as a maintainer of the GFS2 file system.
> > It also changes the development repository to a shared location rather
> > than Steve Whitehouse's private location.
>
> Please also consider letting the linux-next maintainer know :-)
>
> i.e. does this mean I should change the repo/branch I fetch into
> linux-next each day and should I add you to the contacts?
> --
> Cheers,
> Stephen Rothwell sfr at canb.auug.org.au
>
Hi Stephen,
Yes, indeed. I was going to let you know as soon as I got things set up.
Unfortunately, I've been pulled in a lot of directions lately.
I've set up a "for-next" branch from which you can do your daily fetch:
pub/scm/linux/kernel/git/gfs2/linux-gfs2.git
Currently it's empty, and yes, please add me to the contacts.
Regards,
Bob Peterson
Red Hat File Systems
WARNING: multiple messages have this Message-ID (diff)
From: Bob Peterson <rpeterso@redhat.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-fsdevel@vger.kernel.org, cluster-devel <cluster-devel@redhat.com>
Subject: Re: [PATCH] Add myself (Bob Peterson) as a maintainer of GFS2
Date: Tue, 17 Feb 2015 16:06:44 -0500 (EST) [thread overview]
Message-ID: <2095172778.14833591.1424207204509.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20150217013408.6025d2f9@canb.auug.org.au>
----- Original Message -----
> Hi Bob,
>
> On Mon, 16 Feb 2015 09:20:56 -0500 (EST) Bob Peterson <rpeterso@redhat.com>
> wrote:
> >
> > This patch adds Bob Peterson as a maintainer of the GFS2 file system.
> > It also changes the development repository to a shared location rather
> > than Steve Whitehouse's private location.
>
> Please also consider letting the linux-next maintainer know :-)
>
> i.e. does this mean I should change the repo/branch I fetch into
> linux-next each day and should I add you to the contacts?
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
>
Hi Stephen,
Yes, indeed. I was going to let you know as soon as I got things set up.
Unfortunately, I've been pulled in a lot of directions lately.
I've set up a "for-next" branch from which you can do your daily fetch:
pub/scm/linux/kernel/git/gfs2/linux-gfs2.git
Currently it's empty, and yes, please add me to the contacts.
Regards,
Bob Peterson
Red Hat File Systems
next prev parent reply other threads:[~2015-02-17 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <879922160.13310263.1424096327211.JavaMail.zimbra@redhat.com>
2015-02-16 14:20 ` [Cluster-devel] [PATCH] Add myself (Bob Peterson) as a maintainer of GFS2 Bob Peterson
2015-02-16 14:20 ` Bob Peterson
2015-02-16 14:22 ` [Cluster-devel] " Steven Whitehouse
2015-02-16 14:22 ` Steven Whitehouse
2015-02-16 14:29 ` Carlos Maiolino
2015-02-16 14:29 ` Carlos Maiolino
2015-02-16 14:34 ` [Cluster-devel] " Stephen Rothwell
2015-02-16 14:34 ` Stephen Rothwell
2015-02-17 21:06 ` Bob Peterson [this message]
2015-02-17 21:06 ` Bob Peterson
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=2095172778.14833591.1424207204509.JavaMail.zimbra@redhat.com \
--to=rpeterso@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.