diff options
| author | Guido Günther <agx@sigxcpu.org> | 2012-01-12 18:47:35 +0100 |
|---|---|---|
| committer | Guido Günther <agx@sigxcpu.org> | 2012-01-12 18:47:35 +0100 |
| commit | 0206963b247d41987796407feebfc51fec99a10a (patch) | |
| tree | 37f24eae021077ffa6dc05dda54944c9147f1452 /development | |
| parent | fa29b132397e20ac96b7245781f182bf0bad839a (diff) | |
Fix typo.
Thanks to Jari Aalto
Diffstat (limited to 'development')
| -rw-r--r-- | development/debian_packages_in_git.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/development/debian_packages_in_git.mdwn b/development/debian_packages_in_git.mdwn index f7c71cb..9193161 100644 --- a/development/debian_packages_in_git.mdwn +++ b/development/debian_packages_in_git.mdwn @@ -21,7 +21,7 @@ Assuming the Debian source package has it's patches in *debian/patches* and thes cd $REPO gbp-pq import -* This will switch you to the patch-queue branch automatically. If you stared from *master* the patch-queue branch will be called *patch-queue/master*. +* This will switch you to the patch-queue branch automatically. If you started from *master* the patch-queue branch will be called *patch-queue/master*. * Now you can work on the patch-queue branch (add, remove, rebase, test) to get your patches into shape: * To add what will later become a patch in *debian/patches/* simply make a commit. The first line of the commit message will become the patch name later. The following lines include the details of what the patch does. * To remove or edit commits use *git rebase -i master*. The [git documentation][] explains how to work with git-rebase. |