Filewatcher File Search File Search
Catalog
Content Search
» » » » » git-core_1.7.0.4-1_i386.deb » Content »
pkg://git-core_1.7.0.4-1_i386.deb:5622640/usr/share/doc/git-core/  info  control  downloads

git-core - fast, scalable, distributed revision control system…  more info»

README.source

git-core source for Debian
--------------------------

The git-core Debian package sources are available through git, and
through 'apt-get source git-core'.  Getting the sources through git
should be preferred:

 # apt-get install git-core  # if not yet done

 $ git clone http://smarden.org/git/git.git/
 $ cd git

After cloning the repository, you have checked out the debian-sid
branch, ready to be used by dpkg-buildpackage, e.g.

 $ dpkg-buildpackage -i -rfakeroot -uc -us

If you want to make changes in the ./debian/ subdirectory, this is the
correct branch to work on.  After making changes, document them in
debian/changelog, and commit through 'git add' and 'git commit', or 'git
commit -a', or similar.  If you think the changes should be incorporated
into the standard Debian package, create the patch[es] through 'git
format-patch', and send them to the Debian Bug Tracking System, e.g.

 $ vi debian/rules
 $ debchange -pi
 $ git commit -a
 $ git format-patch HEAD^


If you want to make changes to the upstream git sources, first checkout
the release+patches branch

 $ git checkout -b release+patches origin/release+patches

The release+patches branch holds patches on top of the current release
version that is packaged for Debian/unstable. The current release
version is available in the release branch.  If you are interested, you
can checkout this branch too

 $ git checkout -b release origin/release

When releasing a new Debian package based on a new upstream release, the
release branch will be fastforwarded, and the release+patches branch is
rewound and rebased on the new HEAD of the release branch.  This is done
by

 $ git checkout release
 $ git merge v1.6.5
 $ git checkout release+patches
 $ git rebase release

You generally don't need to do that, but beware that the release+patches
branch is rewound occasionally.

After checking out the release+patches branch, make the desired changes
to the upstream sources, and commit them.  To integrate the changes into
the Debian package, extract these changes, and change to the debian-sid
branch (Note: the file extension for the patches is '.diff', use 'git
config --add format.suffix .diff' to make that the default)

 $ git format-patch release..release+patches
 $ git checkout debian-sid

Now move the extracted patches into the debian/diff/ directory, add a
meaningful message to debian/changelog, and commit the changes to the
debian-sid branch

 $ mv ????-*.diff debian/diff/
 $ git add debian/diff
 $ debchange -pi
 $ git add debian/changelog
 $ git commit

Again, if you think the changes should be incorporated into the standard
Debian package, create the patch[es] from the debian-sid branch through
'git format-patch', send them to the Debian Bug Tracking System.

 -- Gerrit Pape <pape@smarden.org>  Tue, 13 Oct 2009 00:07:39 +0000
Results 1 - 1 of 1
Help - FTP Sites List - Software Dir.
Search over 15 billion files
© 1997-2017 FileWatcher.com