[Dctrl-tools-devel] Switching version control again

Antti-Juhani Kaijanaho antti-juhani at kaijanaho.fi
Sat Oct 27 18:08:23 UTC 2007


I've switched version control for dctrl-tools (again).  The master
repository lives now in a Git repository in Alioth's collab-maint area,
with direct push access to all Debian developers and some other guest

For information on how to use Git, see

There is some project-specific information in README.Debian of the next
upload.  I'm including a portion of the file below for your convenience.

Source is managed with git under collab-maint/dctrl-tools.git.  If you
are a Debian developer or have collab-maint guest privileges, you can
  git clone ssh://USERNAME@git.debian.org/git/collab-maint/dctrl-tools.git
For anonymous checkouts, use
  git clone http://git.debian.org/git/collab-maint/dctrl-tools.git

Anybody may submit proposed changes as git-format-patch(1) mails to
the mailing list.

Rules of conduct for people with push access to the repository:

  - Commits should be signed off by the submitter and anybody who
    contributed copyrightable stuff to that commit; a line of the form

      Signed-off-by: Contributor's Name <contributors at email.example>

    in the commit message signifies that the contributor identified on
    that line asserts the Developer's Certificate of Origin 1.1 for
    that particular contribution.

    The authoritative version of the Developer's Certificate of Origin
    for this project is in the Git blob
    c930ac94c745efafe5a6fb4bbe12def76b3af994; Antti-Juhani Kaijanaho
    believes that it is identical to the document of the same name
    used in Linux and other projects.  That blob can be accessed in a
    Git repository that contains it by the command git-cat-file blob

  - The maintainer reserves the right to veto changes; it is good form
    to discuss nontrivial changes on the mailing list (see above) before
    pushing so no reverts have to be made.

  - Simple bugfixes and translation updates may be pushed by anybody
    at any time.

  - Anything committed or merged to master (and any release
    maintenance branches) must compile and pass the test suite at
    least on the committer or merger's development machine; use topic
    branches for instable development.

  - Include an update of debian/changelog in your commits.  One-line
    summary of the commit is sufficient, as you can elaborate in the
    commit log and in comments you might add to the source.
  - Make sure that the distribution in debian/changelog is UNRELEASED
    unless the commit is about preparing a release; the top line in
    debian/changelog should look like

      dctrl-tools (2.12) UNRELEASED; urgency=low

    (where 2.12 is the expected version number of the next release,
    and "low" may be replaced by any other valid urgency value).

Antti-Juhani Kaijanaho, Jyväskylä, Finland
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/dctrl-tools-devel/attachments/20071027/a848d506/attachment.pgp 

More information about the Dctrl-tools-devel mailing list