On Fri, 2004-08-13 at 23:26 +0200, Mikael Hallendal wrote: > Personally I always (I don't think I have messed up yet) do a "cd po && > rm *.po && cvs up" after I've run "make dist". It's a little bit of a > hassle but not nearly as big as it is getting conflicts... 2) do a 'cp -a po po.save'. When making a tarball the auto stuff will modify the po files and we don't want to commit the modifications 3) run autogen.sh 4) type 'make dist' ... 9) back in your cvs directory restore the po.save/ directory to the po/ directory 10) commit the changes to configure.in and ChangeLog 11) tag the release Seems to work fine. --d -- http://davyd.ucc.asn.au/ PGP Fingerprint <http://davyd.ucc.asn.au/pgp> 08B0 341A 0B9B 08BB 2118 C060 2EDD BB4F 5191 6CDA
Attachment:
signature.asc
Description: This is a digitally signed message part