Dgit: forkcheck_*: break out from setup_sigwarn

[dgit.git] / README.dsc-import

diff --git a/README.dsc-import b/README.dsc-import
index 4bcf7fcc50c24513856fd9eb3383e68577fbf8f7..1ec53b037aab4804b94f6767a6fddb7f07cc3777 100644 (file)
--- a/README.dsc-import
+++ b/README.dsc-import
@@ -17,7 +17,7 @@ interface could be designed, which is doubtful):
   Dpkg::Compression to get at the tarball.
 
   Each input tarball unpack will be done separately, and will be
   Dpkg::Compression to get at the tarball.
 
   Each input tarball unpack will be done separately, and will be

-  followed by git-add and git-write tree, to obtain a git tree object
+  followed by git add and git write-tree, to obtain a git tree object

   corresponding to the tarball contents.
 
   That tree object will be made into a commit object with no parents.
   corresponding to the tarball contents.
 
   That tree object will be made into a commit object with no parents.


@@ -80,7 +80,7 @@ This has the following properties:
   commit.  So eg `git blame' will show synthetic commits corresponding
   to the correct parts of the input source package.
 
   commit.  So eg `git blame' will show synthetic commits corresponding
   to the correct parts of the input source package.
 

-* It is possible to `git-cherry-pick' etc. commits representing `3.0
+* It is possible to `git cherry-pick' etc. commits representing `3.0

   (quilt)' patches.  It is even possible fish out the patch stack as
   git branch and rebase it elsewhere etc., since the patch stack is
   represented as a contiguous series of commits which make only the
   (quilt)' patches.  It is even possible fish out the patch stack as
   git branch and rebase it elsewhere etc., since the patch stack is
   represented as a contiguous series of commits which make only the