Bug#930922: dgit: combination of -wgf and --include-dirty nukes untracked files

2019-06-30 Thread Sean Whitton
Hello, On Sat 29 Jun 2019 at 03:36PM +01, Ian Jackson wrote: > Sean Whitton writes ("Re: Bug#930922: dgit: combination of -wgf and > --include-dirty nukes untracked files"): >> On Mon 24 Jun 2019 at 12:02pm +0100, Ian Jackson wrote: >> >> A possible al

Bug#930922: dgit: combination of -wgf and --include-dirty nukes untracked files

2019-06-29 Thread Ian Jackson
Sean Whitton writes ("Re: Bug#930922: dgit: combination of -wgf and --include-dirty nukes untracked files"): > On Mon 24 Jun 2019 at 12:02pm +0100, Ian Jackson wrote: > >> A possible alternative would be to actually add --include-all-dirty, but > >> the problem in

Bug#930922: dgit: combination of -wgf and --include-dirty nukes untracked files

2019-06-29 Thread Sean Whitton
Hello, On Mon 24 Jun 2019 at 12:02pm +0100, Ian Jackson wrote: >> A possible alternative would be to actually add --include-all-dirty, but >> the problem in #914317 suggests that might not be a great idea. > > Your --include-all-dirty is roughly equivalent to -wn or -wdd ? If -wn and -wdd imply

Bug#930922: dgit: combination of -wgf and --include-dirty nukes untracked files

2019-06-24 Thread Ian Jackson
Sean Whitton writes ("Bug#930922: dgit: combination of -wgf and --include-dirty nukes untracked files"): > I agree that this is useful behaviour, but it strikes me as inconsistent > UX. If you don't pass --include-dirty, then dgit treats changes to > tracked files and

Bug#930922: dgit: combination of -wgf and --include-dirty nukes untracked files

2019-06-22 Thread Sean Whitton
control: tag -1 + patch Hello, On Sat 22 Jun 2019 at 04:32pm +0100, Ian Jackson wrote: > Sean Whitton writes ("Bug#930922: dgit: combination of -wgf and > --include-dirty nukes untracked files"): >> The description of --include-dirty says that it tells dgit to "inclu

Bug#930922: dgit: combination of -wgf and --include-dirty nukes untracked files

2019-06-22 Thread Ian Jackson
Sean Whitton writes ("Bug#930922: dgit: combination of -wgf and --include-dirty nukes untracked files"): > The description of --include-dirty says that it tells dgit to "include > the changes from your working tree". However, with -wgf, what it > actually does is

Bug#930922: dgit: combination of -wgf and --include-dirty nukes untracked files

2019-06-22 Thread Sean Whitton
Hello, On Sat 22 Jun 2019 at 04:08pm +0100, Sean Whitton wrote: > The description of --include-dirty says that it tells dgit to "include > the changes from your working tree". However, with -wgf, what it > actually does is include changes to files that have already been > committed, but not chan

Bug#930922: dgit: combination of -wgf and --include-dirty nukes untracked files

2019-06-22 Thread Sean Whitton
Package: dgit Version: 8.3 Severity: important Hello, The description of --include-dirty says that it tells dgit to "include the changes from your working tree". However, with -wgf, what it actually does is include changes to files that have already been committed, but not changes in the form of