Differences between revisions 4 and 5
Revision 4 as of 2007-09-16 12:15:20
Size: 1344
Comment: Added more details on commiter git clone command
Revision 5 as of 2007-09-16 12:29:49
Size: 1490
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
   * {{{git clone ssh://git.debian.org/git/dpkg/dpkg.git}}}
   * or {{{git clone ssh://<usernameOnAlioth>@git.debian.org/git/dpkg/dpkg.git}}}, if your username on alioth is different from the one on your machine (eg: I'm sc on my linux box and sc-guest on alioth)
 * For anonymous: {{{git clone git://git.debian.org/git/dpkg/dpkg.git}}}
   * {{{git clone gti+ssh://git.debian.org/git/dpkg/dpkg dpkg}}}
   * or {{{git clone git+ssh://<usernameOnAlioth>@git.debian.org/git/dpkg/dpkg dpkg}}}, if your username on alioth is different from the one on your machine (eg: I'm sc on my linux box and sc-guest on alioth)
 * For anonymous: {{{git clone git://git.debian.org/git/dpkg/dpkg dpkg}}}

'''NOTE''': dpkg at the end of the command let git create a directory named dpkg under the directory where you execute the command.

Git usage in the dpkg team

URLs

  • For committers:
    • git clone gti+ssh://git.debian.org/git/dpkg/dpkg dpkg

    • or git clone git+ssh://<usernameOnAlioth>@git.debian.org/git/dpkg/dpkg dpkg, if your username on alioth is different from the one on your machine (eg: I'm sc on my linux box and sc-guest on alioth)

  • For anonymous: git clone git://git.debian.org/git/dpkg/dpkg dpkg

NOTE: dpkg at the end of the command let git create a directory named dpkg under the directory where you execute the command.

Generic recommendations

  • When you write commit messages, try to follow the recommended format:

First line should be a small summary.

This is the long description of the change. Leave a blank
line between the summary line and the long description.
  • If you're working on a patch that will take some time to be merged, better work on it in a private topic branch that you can rebase (later and as many times as you want) before merging it in the master branch and pushing it. This will avoid cluttering the history with merge commits.
  • Use git 1.5.x at least. If you run etch there are backports on [http://www.backports.org backports.org].

How to release

  • You should create an annotated tag (non-annotated tags are forbidden by a hook anyway). You can even GPG-sign it.

For translators

TODO: Check with bubulle and others what kind of instructions we should be recommending.