Bug#675790: "dch -r" refuses to proceed

[Harald Dunkel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/03/12 21:13, James McCoy wrote:
> 
> No, it's not a misunderstanding.  Just make vi write the file again (:wq).  We use the modification time to determine whether the changes are acceptable.

Of course I see that you use the modification date to check if
the changelog file was modified, but there is no reason for this
check on "dch -r", since we know for sure that dch had changed it.

> 
> Alternatively, you can one of the options suggested in the man page. Either "dch -r """ (i.e., run -r and supply an empty changelog message) or use --no-force-save-on-release.
> 

So you mean that all Debian developers using dch have to add empty
comments or long command line options, just to avoid some code
rework in dch?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAk/LxScACgkQUTlbRTxpHjei6ACfQa5i67uOs+MzhB+PA+TnIfY0
FNwAnAhgMWZxtqHtONfOG884L1l9HpFJ
=8A3i
-----END PGP SIGNATURE-----