From: Al Viro <viro@ZenIV.linux.org.uk>
To: Mike Marshall <hubcap@omnibond.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Martin Brandenburg <martin@omnibond.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: Orangefs, v4.5 and the merge window...
Date: Sat, 26 Mar 2016 15:50:09 +0000 [thread overview]
Message-ID: <20160326155009.GQ17997@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CAOg9mSQxhRtQXNjF61ukub2O27UTx3anEtZTA881cF-h0F2dyw@mail.gmail.com>
On Sat, Mar 26, 2016 at 11:34:22AM -0400, Mike Marshall wrote:
> OK... I think this is what you're after:
>
> $ git request-pull ko/for-next
> git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux.git
> for-next
>
> The following changes since commit 45996492e5c85aa0ac93a95d1b2d1ed56851c865:
>
> orangefs: fix orangefs_superblock locking (2016-03-26 07:22:00 -0400)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux.git for-next
>
> for you to fetch changes up to 45996492e5c85aa0ac93a95d1b2d1ed56851c865:
>
> orangefs: fix orangefs_superblock locking (2016-03-26 07:22:00 -0400)
Er... That ought to have generated shortlog and diffstat as well; the point
is mostly to see what's intended to be included into pull.
See "16) Sending "git pull" requests" in Documentation/SubmittingPatches:
| A pull request should also include an overall message saying what will be
| included in the request, a "git shortlog" listing of the patches
| themselves, and a diffstat showing the overall effect of the patch series.
| The easiest way to get all this information together is, of course, to let
| git do it for you with the "git request-pull" command.
next prev parent reply other threads:[~2016-03-26 15:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 20:18 Orangefs, v4.5 and the merge window Mike Marshall
2016-03-11 21:47 ` Al Viro
2016-03-11 22:35 ` Mike Marshall
2016-03-14 21:03 ` Mike Marshall
2016-03-26 0:21 ` Al Viro
2016-03-26 1:00 ` Mike Marshall
[not found] ` <CA+55aFzLC_pdj_ds82YYab5D7jpYMj26s0Frofxxhk=j7SqnjA@mail.gmail.com>
2016-03-26 1:01 ` Al Viro
2016-03-26 1:07 ` Mike Marshall
[not found] ` <CA+55aFysWS9mP+QgfAR6LZpEbkp61MUPQu0zDoq7cafmr3M8SA@mail.gmail.com>
2016-03-26 3:55 ` Mike Marshall
2016-03-26 4:30 ` Al Viro
2016-03-26 12:07 ` Mike Marshall
2016-03-26 14:47 ` Al Viro
2016-03-26 15:34 ` Mike Marshall
2016-03-26 15:50 ` Al Viro [this message]
2016-03-26 17:36 ` Mike Marshall
2016-03-26 18:28 ` Al Viro
2016-03-26 18:37 ` Al Viro
2016-03-26 19:00 ` Mike Marshall
2016-03-26 19:51 ` Linus Torvalds
2016-03-26 20:47 ` Mike Marshall
2016-03-26 21:00 ` Linus Torvalds
2016-03-26 1:02 ` Mike Marshall
2016-03-15 4:04 ` Martin Brandenburg
2016-03-15 16:45 ` Martin Brandenburg
2016-03-17 20:45 ` [PATCH] orangefs: getattr work (was: Re: Orangefs, v4.5 and the merge window...) 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=20160326155009.GQ17997@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hubcap@omnibond.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=martin@omnibond.com \
--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).