Signed-off-by: Nicholas D Steeves <nsteeves@gmail.com>
=head1 WHAT KIND OF CHANGES AND COMMITS TO MAKE
When preparing an NMU, the git commits you make on the dgit branch
=head1 WHAT KIND OF CHANGES AND COMMITS TO MAKE
When preparing an NMU, the git commits you make on the dgit branch
-should be simple linear series of commmits with good commit messages.
+should be simple linear series of commits with good commit messages.
The commit messages will be published in various ways,
including perhaps being used as the cover messages for
The commit messages will be published in various ways,
including perhaps being used as the cover messages for
+generated quilt patches.
Do not make merge commits.
Do not try to rebase to drop patches - if you need to revert a
Do not make merge commits.
Do not try to rebase to drop patches - if you need to revert a
Debian package builds are often quite messy:
they may modify files which are also committed to git,
Debian package builds are often quite messy:
they may modify files which are also committed to git,
-or leave outputs and teporary files not covered by C<.gitignore>.
+or leave outputs and temporary files not covered by C<.gitignore>.
If you always commit,
you can use
If you always commit,
you can use