Re: [PATCH v2 0/2] Remove duplicate code from module_clone()

2017-03-09 Thread Brandon Williams
On 03/09, Valery Tolstov wrote: > > The usual protocol would be to rebase off of Stefan's series and build > > on that (assuming you have a dependency against his series), indicating > > that you are doing as such in your cover letter. > > So, should I send only my patch, or current format (patch

Re: Re: [PATCH v2 0/2] Remove duplicate code from module_clone()

2017-03-08 Thread Valery Tolstov
> The usual protocol would be to rebase off of Stefan's series and build > on that (assuming you have a dependency against his series), indicating > that you are doing as such in your cover letter. So, should I send only my patch, or current format (patch and dependency) is acceptalbe? Regards,

Re: [PATCH v2 0/2] Remove duplicate code from module_clone()

2017-03-08 Thread Brandon Williams
On 03/09, Valery Tolstov wrote: > > Then the next step (as outlined by Documentation/SubmittingPatches) > > is to figure out how to best present this to the mailing list; I think the > > best > > way is to send out a patch series consisting of both of these 2 patches, > > the

[PATCH v2 0/2] Remove duplicate code from module_clone()

2017-03-08 Thread Valery Tolstov
> Then the next step (as outlined by Documentation/SubmittingPatches) > is to figure out how to best present this to the mailing list; I think the > best > way is to send out a patch series consisting of both of these 2 patches, > the "connect_work_tree_and_git_dir: safely create leading