Fix manpage typo `dig' for `dgit'.

diff --git a/debian/changelog b/debian/changelog
index 065fcf60fcaf35df59e7a938314422074cc698e3..a9c7cbb60e715eeb244330e051789156310f3dcc 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,6 @@
 dgit (1.2~~) UNRELEASED; urgency=low
 
-  * 
+  * Fix manpage typo `dig' for `dgit'.
 
  --
 

diff --git a/dgit.1 b/dgit.1
index 88e98128b43a404d121ec17b6570a36ba23271b1..f92cf4885ddd2ffd783e68afbb638ccfbfec38e3 100644 (file)
--- a/dgit.1
+++ b/dgit.1
@@ -610,7 +610,7 @@ tracking branch.  Then somehow, using your other git history
 plus appropriate diffs and cherry picks from the dgit remote tracking
 branch, construct a git commit whose tree corresponds to the tree to use for the
 next upload.  If that commit-to-be-uploaded is not a descendant of the
-dig remote tracking branch, check it out and say
+dgit remote tracking branch, check it out and say
 .BR "git merge -s ours remotes/dgit/dgit/" \fIsuite\fR;
 that tells git that we are deliberately throwing away any differences
 between what's in the archive and what you intend to upload.