Re: [Pcmanfm-develop] [PATCH] Do not track `po/pcmanfm.pot` in Git

[Martin B. / b. <br...@bs...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2012-10-18 18:45, PCMan wrote:
> On Tue, Oct 16, 2012 at 4:58 PM, Paul Menzel 
> <pau...@us...> wrote:
>> Date: Tue, 16 Oct 2012 10:53:15 +0200
>> 
>> Wanting to run Git commands after `make clean`, Git complains and
>> the file has to be restored to make Git happy.
>> 
>> Cannot rebase: You have unstaged changes. Please commit or stash
>> them.
>> 
>> Not letting Git track this generated file solves this issue.
>> 
> Basically, this file should not be removed from git even it's
> annoying. Currently, in our translation workflow, the translation
> system pootle is now integrated with out git repos and relies on
> these *.pot files. Besides, it's a common practice to put the *.pot
> files in git. So, I don't think that we should apply the patches.

Just to reiterate what was stated on IRC regarding POT files in git.

We don't NEED them for Pootle to work but the way I work with Pootle
and our git repositories I use the POT for some status things.
And if there are no real technical problems with having the POT file
in git I oppose the removal of the file. It serves a purpose.

If the file is posing problem after build you could either try to fix
the build process or ignore it and use git checkout to get the
repository version of the file.


But this has all been settled on IRC, I just wanted to bring it up on
list to not leave the conversation out of this context.

- -- 
brother
http://sis.bthstudent.se
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBCAAGBQJQhT0MAAoJEJbdSEaj0jV7N8sH/jzlstiq1/KmTX4zAOxLEOnK
o3TCHmBeete181XSOCE1v/AKVsOkwgpRpHMKV9ACaS5ROrG7Pjz5KbKLl4HvSflQ
N63Y0siPQTx8y8wEKX25xgDlE5UdiiU9oFU+eiL2jUCciqf/7jC2w7vCLQr0suVb
QuP77yao8URspUV4v+QwcVDdrkGE5RJbdIb/jRoynHnOMtXrqZuHynNwEAaDA35z
QP4NFLAPaLZycyLmXdX3rc9tG+BZ4C7iXHOi0Qno4nY4hLyE0iao0i8TTLA9vBNY
r2c6QjhCGWunCNOQSse0nGV1y4N3PNig+5SN3a5Pqo5E/JIta4+pzt0eCNeajNo=
=pwLe
-----END PGP SIGNATURE-----