Your message dated Tue, 21 Aug 2018 14:20:50 +0100
with message-id <[email protected]>
and subject line Re: Bug#886626: Patches for this manpage bug and other updates
has caused the Debian Bug report #886626,
regarding dgit-maint-*(7) should mention `dgit push-source`
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
886626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886626
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dgit
Version: 4.2
Severity: wishlist
Hello,
At various points `dgit push-source` should probably be mentioned,
perhaps in those cases where it means one can avoid --rm-old-changes.
In particular, dgit-maint-gbp(7) should emphasise that when doing a
source-only upload, the entire building/signing/tagging/uploading
process can be replaced with a single invocation of `dgit --gbp
push-source`. This is a material simplification to many people's
existing workflows, that additionally publishes a more usable history to
dgit-repos.
--
Sean Whitton
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: dgit
Source-Version: 6.2
These patches were included some time ago.
(I hope I have this bug close syntax right...)
Ian.
--
Ian Jackson <[email protected]> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
--- End Message ---
