Re: RFC: How about using MRs to communicate the diffs for NMUs with an MR

2019-11-03 Thread Sam Hartman
> "Sean" == Sean Whitton writes: Sean> Hello, Sean> On Thu 31 Oct 2019 at 12:00PM +01, Gert Wollny wrote: >> "Then, you either prepare the NMU in a fork of the original >> packaging repository and submit a merge request referencing the >> bug you are fixing, or send a pat

Re: RFC: How about using MRs to communicate the diffs for NMUs with an MR

2019-11-02 Thread Gert Wollny
Am Freitag, den 01.11.2019, 00:48 +0100 schrieb gregor herrmann: > On Thu, 31 Oct 2019 13:54:11 -0700, Sean Whitton wrote: > > > On Thu 31 Oct 2019 at 12:00PM +01, Gert Wollny wrote: > > > "Then, you either prepare the NMU in a fork of the original > > > packaging > > > repository and submit a mer

Re: RFC: How about using MRs to communicate the diffs for NMUs with an MR

2019-10-31 Thread gregor herrmann
On Thu, 31 Oct 2019 13:54:11 -0700, Sean Whitton wrote: > On Thu 31 Oct 2019 at 12:00PM +01, Gert Wollny wrote: > > "Then, you either prepare the NMU in a fork of the original packaging > > repository and submit a merge request referencing the bug you are > > fixing, or send a patch containing the

Re: RFC: How about using MRs to communicate the diffs for NMUs with an MR

2019-10-31 Thread Sean Whitton
Hello, On Thu 31 Oct 2019 at 12:00PM +01, Gert Wollny wrote: > "Then, you either prepare the NMU in a fork of the original packaging > repository and submit a merge request referencing the bug you are > fixing, or send a patch containing the differences between the current > package and your prop

RFC: How about using MRs to communicate the diffs for NMUs with an MR

2019-10-31 Thread Gert Wollny
Dear all, with salsa and most of the packaging going on in git I wonder whether we could add using MRs as an alternative way to communicate the diff that is related to an NMU instead of adding a patch to the related bug. When preparing an NMU people might already be using git anyway, and if one