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) ---------------------------------------------------------------- I understand about setting up URL types in your second paragraph, and I have a github tree that I keep current, I thought we all sort of focused on kernel.org being the "canonical place" around here... I'll pay more attention to other pull/push requests on the mailing list... -Mike On Sat, Mar 26, 2016 at 10:47 AM, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote: > On Sat, Mar 26, 2016 at 08:07:58AM -0400, Mike Marshall wrote: >> Yay, Al, that did it, thanks! >> >> I've tested, and updated the for-next branch at kernel.org... >> >> Linus, if it is not too late, can you pull from: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux.git >> for-next > > Shortlog and diffstat would be a good idea... Something like the output of > git request-pull origin git://git.kernel.org/pub/scm/linux/kernel/git/hubcap/linux.git for-next > > Longer term you want a remote to avoid typing that crap every time; just be > careful to set both url (git:// one) and pushurl (ssh:// equivalent) for > it. The former will be usable for somebody to pull from you (and go into > the output of git request-pull), the latter is obviously for pushes... -- 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
