RE: [PATCH v3 00/21] git-p4: Various code tidy-ups
> Perhaps looking for "Note from the maintainer" in the list archive would find
> more info, hopefully?
Thanks for the info. I'll check it out.
Show 10 quoted lines
> > The SubmittingPatches guide talks about branching off master, and
> merging the prerequisite topic branches. For this patch-set I will need:
> >
> > * jh/p4-spawning-external-commands-cleanup
> > * jh/p4-fix-use-of-process-error-exception
> > * ab/config-based-hooks-2
>
> Correct. FWIW, I was updating the "What's cooking" report and am planning
> to propose merging the first two to 'master' either today or tomorrow as part
> of the first batch, and the last one in the next batch after a few days.
Good stuff. It sounds like the easiest thing is for me to resubmit some time next week as and when the patch-sets hit master.
> You'd use "git format-patch [...] $BASE" where $BASE is the commit you'll
> locally create by merging these prerequisite topics to 'master'.
Makes sense. And I suppose the cover letter would have to list out the dependencies? - because otherwise you won't see any merge commits in the emails.
Joel
Joel Holdsworth <jholdsworth@nvidia.com>