Bug#886969: Bug#886625: push-source should be usable no matter the state of the working tree

Hello, On Thu, Jun 21 2018, Ian Jackson wrote: >> This might be a reason to not remove but instead firmly deprecate >> build-source, until one can dgit push to security-master. > > I don't really mind deprecating it. Dropping it entirely would be a > different matter. It might be embedded in

Bug#886969: Bug#886625: push-source should be usable no matter the state of the working tree

Sean Whitton writes ("Bug#886969: Bug#886625: push-source should be usable no matter the state of the working tree"): > On Sun, Apr 22 2018, Sean Whitton wrote: > > I thought of a case where a .dsc is not sufficient and one needs a > > .changes: services like .

Bug#886969: Bug#886625: push-source should be usable no matter the state of the working tree

Hello, On Sun, Apr 22 2018, Sean Whitton wrote: > I thought of a case where a .dsc is not sufficient and one needs a > .changes: services like . I thought of one more case recently: uploading to security-master. You can't dgit push there yet, so you need an

Bug#886969: Bug#886625: push-source should be usable no matter the state of the working tree

Hello, On Mon, Jan 08 2018, Ian Jackson wrote: > Mattia Rizzolo writes ("Bug#886625: push-source should be usable no >matter the state of the working tree"): >> On Mon, Jan 08, 2018 at 11:20:08AM +, Ian Jackson wrote: >> > (Now that push-source exists I'm not sure why you would >> >

Bug#886625: push-source should be usable no matter the state of the working tree

control: clone 886625 -2 control: retitle -2 push-source should be usable on arbitrary refs control: block -2 by 886625 On Mon, Jan 08, 2018 at 12:11:26PM +, Ian Jackson wrote: > One often wants to do that with a dirty tree. It would be useful to > be able to do it for refs other than head.

Bug#886625: push-source should be usable no matter the state of the working tree

(resending to the bug) Sean Whitton writes ("Re: Bug#886625: push-source should be usable no matter the state of the working tree"): > On Mon, Jan 08 2018, Ian Jackson wrote: > > I think we should probably retain the current checks that the working > > tree is up to date, to avoid accidents.

Bug#886625: push-source should be usable no matter the state of the working tree

Hello, On Mon, Jan 08 2018, Mattia Rizzolo wrote: > On Mon, Jan 08, 2018 at 11:20:08AM +, Ian Jackson wrote: >> (Now that push-source exists I'm not sure why you would build-source, >> really.) > > To build a .dsc and then pass it to a non supported builder (which > means, anything that is

Bug#886625: push-source should be usable no matter the state of the working tree

Mattia Rizzolo writes ("Bug#886625: push-source should be usable no matter the state of the working tree"): > On Mon, Jan 08, 2018 at 11:20:08AM +, Ian Jackson wrote: > > (Now that push-source exists I'm not sure why you would build-source, > > really.) > > To build a .dsc and then pass it

Bug#886625: push-source should be usable no matter the state of the working tree

On Mon, Jan 08, 2018 at 11:20:08AM +, Ian Jackson wrote: > (Now that push-source exists I'm not sure why you would build-source, > really.) To build a .dsc and then pass it to a non supported builder (which means, anything that is not sbuild or gbp, I think). -- regards,

Bug#886625: push-source should be usable no matter the state of the working tree

Sean Whitton writes ("Bug#886625: push-source should be usable no matter the state of the working tree"): > Package: dgit > Version: 4.2 > Severity: wishlist ... > It would be better if `dgit push-source` could operate on HEAD alone, no > matter the state of the working tree. That would render

Bug#886625: push-source should be usable no matter the state of the working tree

Package: dgit Version: 4.2 Severity: wishlist Hello, In my mind, the command % dgit push-source unstable ought to be as closely analogous as we can make it to the (as yet) fictional command % git push ftp-master HEAD:master One important part of rendering these commands analogous is