diff options
| author | agx <agx@web> | 2009-09-16 23:50:54 +0200 |
|---|---|---|
| committer | Wiki User <wikwik@wiki.sigxcpu.org> | 2009-09-16 23:50:54 +0200 |
| commit | 2d7e547466b03c6c30c934ef14dbe7c84dd16390 (patch) | |
| tree | 6878d97d1d34e0e841d23dc97c63416b41e775ca /development | |
| parent | e40c697a880ca11aa4fd3bc7e06a0d73974024e6 (diff) | |
add gbp-clone
Diffstat (limited to 'development')
| -rw-r--r-- | development/debian_packages_in_git.mdwn | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/development/debian_packages_in_git.mdwn b/development/debian_packages_in_git.mdwn index 5111cb6..e24d249 100644 --- a/development/debian_packages_in_git.mdwn +++ b/development/debian_packages_in_git.mdwn @@ -1,4 +1,6 @@ -## keeping debian/patches on a patch-queue branch +[[!toc]] + +## Keeping debian/patches on a patch-queue branch I'm keeping all patches for a Debian package that is maintained on branch *foo* on a patch-queue branch *patch-queue/foo* since: * one can easily work with the unpatched (*foo*) and patched (*patch-queue/foo*) branches @@ -44,3 +46,6 @@ The easiest way is to not push out any patch-queue/* branches at all. They can b gbp-pq import However you *can* push out patch-queue branches. Other team members must just be aware that that branches in the *patch-queue/* namespace are being rebased frequently. + +## 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](http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.intro.html#GBP.REPOSITORY) explains the terminology. |