diff options
| author | Lucas Nussbaum <lucas@debian.org> | 2015-12-26 10:11:38 +0100 |
|---|---|---|
| committer | Guido Günther <agx@sigxcpu.org> | 2015-12-27 15:13:36 +0100 |
| commit | 41d732175ea5954aa6c56f6c6c9f03af63b74113 (patch) | |
| tree | 77061dfbab40795435680e1ea8c3686eb8c1cb81 /docs | |
| parent | dd1ff6cbda2f1a7e8e653c35fc850b9e417c5344 (diff) | |
Drop irrelevant bits
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/chapters/patches.sgml | 20 |
1 files changed, 0 insertions, 20 deletions
diff --git a/docs/chapters/patches.sgml b/docs/chapters/patches.sgml index e51b9723..47ec938b 100644 --- a/docs/chapters/patches.sgml +++ b/docs/chapters/patches.sgml @@ -167,24 +167,4 @@ Build and test... </screen> </listitem> </itemizedlist> - -Cloning a repository -If you use gbp clone instead of git clone to clone a remote repository it will automatically set up the debian, upstream and pristine-tar branches for you. The manual explains the terminology. - -Keeping a repository up to date -After initially cloning with gbp clone you can run gbp pull to update your debian, upstream and pristine-tar branches from the remote site. So the complete workflow for simple team maintenance looks like this: - -# Initially clone the repo once -gbp clone git://git.debian.org/pkg-libvirt/gtk-vnc.git -cd gtk-vnc -Work on that clone, commit, release, push, etc. Now after a couple of days you want to make more changes but don't know if another developer worked on it. So you do: - -# Update to what others might have pushed -gbp pull -This will update all necessary branches to what other developers might have pushed in the meantime. If you're also using a patch-queue as described above you can refresh that too in one step: - -# Update to what others might have pushed and rebuild patch-queue -gbp pull --redo-pq -This will additionally drop your current patch-queue branch and recreate it from debian/patches. - </para> </chapter> |