---------- Forwarded message ---------- From: Martin Geisler <m...@lazybytes.net> Date: 2009/7/26 Subject: New i18n repositories To: mercurial-de...@selenic.com Cc: wagner.bruna+mercur...@gmail.com <wagner.bruna%2bmercur...@gmail.com>, tobias.b...@gmail.com, fo...@lares.dti.ne.jp, dongsheng.s...@gmail.com, bela...@gmail.com, cedricdu...@free.fr, keram...@ceid.upatras.gr, willie.tw@ gmail.com, Matt Mackall <m...@selenic.com>
Hi everybody, I've moved the repositories for i18n updates: * http://bitbucket.org/mg/hg-i18n-stable/ * http://bitbucket.org/mg/hg-i18n/ The first one will track Matt's stable repository, the second will track Matt's main repository. This means that you can now target either repository with your updates. However, if you begin maintaining a fork of repositories (i.e., a 'xx' and a 'xx-stable' repository) then you must ensure that your 'xx' repository is a *superset* of the 'xx-stable' repository. So when you make a change in 'xx-stable', you will have to pull that over in 'xx' and merge before pushing the changes for me to see. If you don't do this, I'll have to merge your translation and that wont be pretty :-) [What really happens is that I wont pull from your 'xx-stable' repository until you merge it into your 'xx' repository.] You can also just keep working against what is now called hg-i18n and don't worry about this. They you'll get the new strings fast, but wont be able to target the small point releases made between major releases. -- Martin Geisler VIFF (Virtual Ideal Functionality Framework) brings easy and efficient SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/. -- Romain PELISSE, "The trouble with having an open mind, of course, is that people will insist on coming along and trying to put things in it" -- Terry Pratchett http://belaran.eu/
pgpdryKqz2T4r.pgp
Description: PGP signature
