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. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
