[debhelper-devel] [debhelper] 01/01: debhelper.pod: Update the "--remaining" caveat

Niels Thykier nthykier at moszumanska.debian.org
Mon Jan 11 19:09:34 UTC 2016


This is an automated email from the git hooks/post-receive script.

nthykier pushed a commit to branch master
in repository debhelper.

commit 06c54c422ee5d4bee373506ef39cb5ee5861322a
Author: Niels Thykier <niels at thykier.net>
Date:   Mon Jan 11 19:09:18 2016 +0000

    debhelper.pod: Update the "--remaining" caveat
    
    Signed-off-by: Niels Thykier <niels at thykier.net>
---
 debhelper.pod | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/debhelper.pod b/debhelper.pod
index ffd3228..d3cd65c 100644
--- a/debhelper.pod
+++ b/debhelper.pod
@@ -569,10 +569,10 @@ do a full "clean and rebuild" cycle)
 
 =item -
 
-The main caveat is that the B<--remaining> option for B<dh_*> now only
-keeps track of what happened in a single override target.  When all
-the calls to a given B<dh_cmd> command happens in the same override
-target every thing will work as before.
+The main caveat is that B<dh_*> now only keeps track of what happened
+in a single override target.  When all the calls to a given B<dh_cmd>
+command happens in the same override target every thing will work as
+before.
 
 Example of where it can go wrong:
 
@@ -585,7 +585,8 @@ Example of where it can go wrong:
 
 In this case, the call to B<dh_foo --remaining> will I<also> include
 I<my-pkg>, since B<dh_foo -pmy-pkg> was run in a separate override
-target.  If they are run from the same override target, it will work j
+target.  This issue is not limited to B<--remaining>, but also includes
+B<-a>, B<-i>, etc.
 
 =back
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/debhelper/debhelper.git




More information about the debhelper-devel mailing list