-- HP -- ESIEE --


GIT INFORMATION

The CVS repository has now been replaced by a shared git repository. Some infrastructure still needs to be made git-aware, for example there is currently no autobuilder. You can view the shared tree here.

Other git trees of interest include the merge tree, the compat tree and the sym2 tree.

Anonymous read-only access is available to the git repositories. Please see the git tutorial. Debian users can install "cogito" package and use those tools instead.

    git-clone git://git.parisc-linux.org/git/linux-2.6.git parisc-2.6
If firewalls prevent you from using the git daemon, you can also fetch the source using the rsync protocol
    git-clone rsync://git.parisc-linux.org/git/linux-2.6.git parisc-2.6
or via http
    git-clone http://www.parisc-linux.org/git/linux-2.6.git parisc-2.6
The http method is deprecated as it will transfer 100MB of data whenever the shared repository is repacked.

Local Git access - For working repositories on parisc-linux.org

    git-clone -l -s /var/git/linux-2.6.git parisc-2.6
This shares your objects with the ones in the master copy, reducing the amount of space consumed.

Authenticated Git access - Developers with write access to the repository will have an account on the server and use ssh to authenticate themselves.

    git-clone ssh://git.parisc-linux.org/var/git/linux-2.6.git parisc-2.6
Use ssh-agent to avoid having to re-enter the ssh password when pushing or pulling.

After the initial checkout, further updates can be done by simply typing git-pull. If you have write access, git-push origin will commit your changes back to the shared repository.

In order to keep our git tree easy to work with, there are some best practices for developers to follow:

  • Keep history free of merges
  • Merge from Linus' tree regularly
  • Rebase on the top of Linus' tree occasionally
  • If you're going to update the -pa number in the Makefile, do so in a separate commit, so that the changes can be cherry-picked easily without having to hand-edit the diff. You can (and should) push the Makefile commit at the same time as your other commits.
  • Check 'git-log origin..' before you git-push so you don't inadvertently commit something you shouldn't. Immediate unwinds are possible, but qualify as Black Arts.


Developers who have write access agree with and abide by the PA-RISC Linux Acceptable Use Policy.