|author||Ian Jackson <firstname.lastname@example.org>||2015-11-07 13:13:59 +0000|
|committer||Ian Jackson <email@example.com>||2016-07-01 23:53:45 +0100|
No longer tolerate a multitude of .changes files when doing push.
Instead, insist on a single one. This eliminates a potential for a variety of surprises, where dgit would upload something different to the user expected. We no longer need to behave this way because nowadays the sbuild build (which was the real use case, because it would generate a .source and a .ARCH changes as well as the final .multi) renames the intermediate changes files. Also --rm-old-changes helps.
Diffstat (limited to 'dgit.1')
1 files changed, 1 insertions, 2 deletions
@@ -514,8 +514,7 @@ How to set this up is not yet documented.
.BI -C changesfile
Specifies the .changes file which is to be uploaded. By default
dgit push looks for single .changes file in the parent directory whose
-filename suggests it is for the right package and version - or,
-if there is a _multi.changes file, dgit uses that.
+filename suggests it is for the right package and version.
If the specified