From: | Roger Leigh <rleigh(at)codelibre(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: size of .po changesets |
Date: | 2012-08-23 16:08:42 |
Message-ID: | 20120823160842.GB20427@codelibre.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Aug 23, 2012 at 11:21:35AM -0400, Alvaro Herrera wrote:
> Excerpts from Tom Lane's message of jue ago 23 11:01:05 -0400 2012:
>
> >
> > $ git diff --shortstat REL9_0_9 REL9_1_5
> > 3186 files changed, 314847 insertions(+), 210452 deletions(-)
> > $ git diff --shortstat REL9_1_5 REL9_2_BETA4
> > 2037 files changed, 290919 insertions(+), 189487 deletions(-)
> >
> > However, when you look at things a bit closer, these numbers are
> > misleading because they include the .po files, which seem to have huge
> > inter-branch churn --- well in excess of 100000 lines changed per
> > release, at least in git's simpleminded view.
>
> Yeah, IMHO .po files are handled pretty badly by SCMs. I wonder if we
> could reduce the amount of git churn caused by those files by simply
> removing all comment lines from these files as they are exported from
> pgtranslation into postgresql.git? Since they are not "source" for
> postgresql.git anyway, the other one being the canonical repository,
> there doesn't seem to be any point to those lines ... or am I mistaken?
Have you considered adding "--no-location" to XGETTEXT_OPTIONS in
po/Makevars? This stops the massive churn through line renumbering
changes.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-08-23 16:55:46 | Re: default_isolation_level='serializable' crashes on Windows |
Previous Message | Alvaro Herrera | 2012-08-23 15:21:35 | size of .po changesets |