From: Joe Perches <joe@perches.com>
To: Martin Brandenburg <martin@omnibond.com>
Cc: Mike Marshall <hubcap@omnibond.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [git pull] orangefs bugfixes for rc2
Date: Fri, 01 Apr 2016 16:23:46 -0700 [thread overview]
Message-ID: <1459553026.1744.38.camel@perches.com> (raw)
In-Reply-To: <alpine.BSO.2.20.1604011548470.26523@server1.sysblue.org>
Hello Martin.
Here's an orangefs patch I think should be applied:
https://patchwork.kernel.org/patch/8676461/
You were not cc'd on this as you are not listed as a
maintainer for orangefs.
Should you be?
next prev parent reply other threads:[~2016-04-01 23:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 16:17 [git pull] orangefs bugfixes for rc2 Martin Brandenburg
2016-03-31 19:27 ` Linus Torvalds
2016-03-31 21:01 ` Mike Marshall
2016-03-31 21:06 ` Mike Marshall
2016-03-31 22:11 ` Linus Torvalds
2016-03-31 22:59 ` Al Viro
2016-04-01 1:19 ` Theodore Ts'o
2016-04-01 19:49 ` Martin Brandenburg
2016-04-01 22:35 ` Linus Torvalds
2016-04-01 23:29 ` Mike Marshall
2016-04-01 23:23 ` Joe Perches [this message]
2016-04-02 1:32 ` Martin Brandenburg
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=1459553026.1744.38.camel@perches.com \
--to=joe@perches.com \
--cc=hubcap@omnibond.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@omnibond.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox