[updating CC to point to the correct bug, not #928473] Acked-by: / Reviewed-by: Sean Whitton <spwhit...@spwhitton.name>
This is a nice change. On Thu 05 Sep 2019 at 02:57PM +01, Ian Jackson wrote: > Closes: #935443 > Signed-off-by: Ian Jackson <ijack...@chiark.greenend.org.uk> > --- > dgit.1 | 13 +++++++++---- > 1 file changed, 9 insertions(+), 4 deletions(-) > > diff --git a/dgit.1 b/dgit.1 > index 8969e2f2..c270b303 100644 > --- a/dgit.1 > +++ b/dgit.1 > @@ -630,11 +630,16 @@ fails even on ignored untracked files. > This could perhaps be used to detect bugs in your rules clean target. > .TP > .BR -N " | " --new > -The package is or may be new in this suite. Without this, dgit will > +The package is, or may be, new in this suite. Without this, dgit will > refuse to push. > -It may (for Debian, will) be unable to access the git > -history for any packages which have been newly pushed and have not yet > -been published. > +Needing --new is not unusual; for example, > +it is frequently needed for uploading to Debian experimental. > + > +Note that dgit may be unable to access the git > +history for an entirely new package which has not been accepted by > +the archive. > +So for an entirely new package you need to properly coordinate > +with anyone else who might upload. > .TP > .BR --include-dirty > Do not complain if the working tree does not match your git HEAD, -- Sean Whitton
signature.asc
Description: PGP signature
