-=| Dmitry E. Oboukhov, 28.12.2011 10:10:20 +0400 |=- > > >>> Well, all (?) other packages have 3 branches: master, pristine-tar, > >>> upstream. (I also have no idea how pristine-tar works without an > >>> upstream branch, but I leave that to our git experts.) > >> git clone url-to-package package-version > >> cd package-version > >> pristine-tar checkout ../package_version.orig.tar.gz > > > Yup. > > And how do you get new upstream tarballs into the repo? > > (Import on master and run pristine-tar against thet branch?) > > pristine-tar commit path/to/tar.gz tagname > > :) > > I think that 'upstream' branch has meaning if You receive upstream > sources by git, too. But if You have upstream's tar.gz it is worth to > use pristine-tar. In the context of the Perl Group, the upstream branch contains unpacked upstream releases and is not tracking upstream's Git tree. There is a tool, git-import-orig, which can help with both the pristine-tar and upstream branches (plus the upstream/xxx tags). HTH, dam
Attachment:
signature.asc
Description: Digital signature