|author||Ian Jackson <firstname.lastname@example.org>||2016-10-16 12:51:08 +0100|
|committer||Ian Jackson <email@example.com>||2016-10-16 13:11:13 +0100|
git- prefixes: Change `git-foo' to `git foo' in docs and comments
No functional change. Signed-off-by: Ian Jackson <firstname.lastname@example.org>
Diffstat (limited to 'README.dsc-import')
1 files changed, 2 insertions, 2 deletions
diff --git a/README.dsc-import b/README.dsc-import
index 4bcf7fc..1ec53b0 100644
@@ -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
- 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.
@@ -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.
-* 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