1501
Comment: added <<BR>> so there is a clear distinction between git-buildpackage and git
|
1694
adding git commit --amend
|
Deletions are marked like this. | Additions are marked like this. |
Line 37: | Line 37: |
<<BR>> | |
Line 42: | Line 42: |
A typical gotcha is to "git push origin master" instead (and or to forget the --tags push). <<BR>> === git commit --amend === To make it short: it can help you if you edit the same file a few times to figure out what to do, but will keep your commit log clean. The manpage |
|
Line 43: | Line 49: |
git push --all git push --tags |
man git-commit |
Line 46: | Line 51: |
A typical gotcha is to "git push origin master" instead (and or to forget the --tags push). | is elaborate. |
Translation(s): none
Introduction
A lot of git and git-buildpackage commands needed got more than one option, are needed seldom and are hard to remember. This page is supposed to be a reminder, not a detailed explanation. Like: You remember you had to use a git-buildpackage command, but can't find it in your notes any more (and neither online).
git-buildpackage
clone from gitorious for rebuilding
gbp-clone --pristine-tar git@gitorious.org:debian-diaspora/ruby-columnize.git
By cloning like this you will be able to build the package with
git-buildpackage
for example if you want to have a look at the package of someone else.
import new upstream version
If there is a working debian/watch file:
git-import-orig --pristine-tar --uscan
If you need to download a new upstream tarball manually:
git-import-orig --pristine-tar path/to/<new-upstream-version>.tar.gz
git
simple push
To push to gitorious run
A typical gotcha is to "git push origin master" instead (and or to forget the --tags push).
git commit --amend
To make it short: it can help you if you edit the same file a few times to figure out what to do, but will keep your commit log clean. The manpage
man git-commit
is elaborate.