| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Kevin Grittner <kevin(dot)grittner(at)wicourts(dot)gov>, Boszormenyi Zoltan <zb(at)cybertec(dot)at>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: size of .po changesets |
| Date: | 2012-08-24 03:36:45 |
| Message-ID: | 1345779405.9270.5.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2012-08-23 at 11:21 -0400, Alvaro Herrera wrote:
> Yeah, IMHO .po files are handled pretty badly by SCMs.
By SCMs that store diffs internally, perhaps, but Git doesn't, so I
don't think it matters much for storage whether .po files diff well.
> 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?
I don't see this being worth the trouble. It would just make it more
difficult to track where the files are coming from. There could also be
problems with downstream distributors if we are not shipping files in
source form.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2012-08-24 03:46:05 | Re: [WIP] Performance Improvement by reducing WAL for Update Operation |
| Previous Message | Peter Eisentraut | 2012-08-24 03:15:06 | Re: Why does analyze_new_cluster.sh use sleep? |