On Thu, Mar 29, 2018 at 10:20:40PM +0000, Erik Brady -X (brady - ROBERT HALF INTERNATIONAL INC at Cisco) wrote: > I appreciate your time. Quick Q... is there a way to track the patch > through to release? If not I can just scan release notes/etc so no > worries. When the maintainer picks up the patch, he usually says something like "thanks, will queue". Then you can track its progress either by: - fetching from https://github.com/gitster/git, which has all of the topic branches. Yours will be "eb/something", depending what Junio names it. And then you can periodically "git branch -a --contains eb/something" to see it progress through the various integration branches ('pu', 'next', 'master'). The branches are described in the "note from the maintainer" that's sent to the list periodically. E.g.: https://public-inbox.org/git/xmqqy3nt40pq.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx/ - alternatively, you can read the "What's cooking in git.git" messages sent out by the maintainer a few times a week. E.g.: https://public-inbox.org/git/xmqqefkm6s06.fsf@xxxxxxxxxxxxxxxxxxxxxxxxx/ There your eb/something topic will be mentioned, along with the status (where it is in the graduation cycle, what's coming next, and if it's stalled, why). We're in a release freeze right for v2.17 right now, so I'd expect your patch to probably go to the 'maint' track and end up in v2.17.1. Of course somebody else may see something wrong I didn't and ask you to correct it, which would be in a reply to this thread. :) -Peff
