|
|
|
pgwn:26_septembre_2010 [2010/09/28 00:47]
buggy créée |
pgwn:26_septembre_2010 [2010/09/28 01:00] (Version actuelle)
buggy Modif script commit->push |
| <p>Marko (johto) Tiikkaja reviewed Boxuan Zhai's MERGE patch.</p> | <p>Marko (johto) Tiikkaja reviewed Boxuan Zhai's MERGE patch.</p> |
| <p><strong>Correctifs appliqués</strong></p> | <p><strong>Correctifs appliqués</strong></p> |
| | <p>Magnus Hagander a poussé :</p> |
| <ul> | <ul> |
| <li>Magnus Hagander pushed:</li> | |
| <li>Rename README.CVS to README.git and change references in it. | <li>Rename README.CVS to README.git and change references in it. |
| <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=397761827aa3a3ac95b8a60dd21900f7bae88f05">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=397761827aa3a3ac95b8a60dd21900f7bae88f05</a></li> | <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=397761827aa3a3ac95b8a60dd21900f7bae88f05">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=397761827aa3a3ac95b8a60dd21900f7bae88f05</a></li> |
| <li>Add gitignore files for ecpg regression tests. Backpatch to 8.2 as that's how far the structure looks the same. | <li>Add gitignore files for ecpg regression tests. Backpatch to 8.2 as that's how far the structure looks the same. |
| <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=6c137da018ad3ec52c872e0bb88c5968830e58d0">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=6c137da018ad3ec52c872e0bb88c5968830e58d0</a></li> | <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=6c137da018ad3ec52c872e0bb88c5968830e58d0">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=6c137da018ad3ec52c872e0bb88c5968830e58d0</a></li> |
| <li>Robert Haas pushed:</li> | </ul> |
| | <p>Robert Haas a poussé :</p> |
| | <ul> |
| <li>git_topo_order script, to match up commits across branches. This script is intended to substitute for cvs2cl in generating release notes and scrutinizing what got back-patched to which branches. Script by me. Support for --since by Alex Hunsaker. | <li>git_topo_order script, to match up commits across branches. This script is intended to substitute for cvs2cl in generating release notes and scrutinizing what got back-patched to which branches. Script by me. Support for --since by Alex Hunsaker. |
| <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=1b984d43e54a969da26277d913a41ffd5ccfc1e8">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=1b984d43e54a969da26277d913a41ffd5ccfc1e8</a></li> | <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=1b984d43e54a969da26277d913a41ffd5ccfc1e8">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=1b984d43e54a969da26277d913a41ffd5ccfc1e8</a></li> |
| <li>In contrib/fuzzystrmatch/fuzzystrmatch.c, in levenshtein_internal(), describe algorithm a bit more clearly. | <li>In contrib/fuzzystrmatch/fuzzystrmatch.c, in levenshtein_internal(), describe algorithm a bit more clearly. |
| <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=12679b8bc908f941710bed185aa142ad5de539c6">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=12679b8bc908f941710bed185aa142ad5de539c6</a></li> | <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=12679b8bc908f941710bed185aa142ad5de539c6">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=12679b8bc908f941710bed185aa142ad5de539c6</a></li> |
| <li>Tom Lane pushed:</li> | </ul> |
| | <p>Tom Lane a poussé :</p> |
| | <ul> |
| <li>In README.git, trivial typo fix. | <li>In README.git, trivial typo fix. |
| <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=eacc4a3b9a7ea8a2608cb95981646f947efed625">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=eacc4a3b9a7ea8a2608cb95981646f947efed625</a></li> | <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=eacc4a3b9a7ea8a2608cb95981646f947efed625">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=eacc4a3b9a7ea8a2608cb95981646f947efed625</a></li> |
| <li>Improve git_changelog as per discussion with Robert Haas. 1. Resurrect the behavior where old commits on master will have Branch: labels for branches sprouted after the commit was made. I'm still dubious about this mode, but if you want it, say --post-date or -p. 2. Annotate the Branch: labels with the release or branch in which the commit was publicly released. For example, on a release branch you could see Branch: REL8_3_STABLE Release: REL8_3_2 [92c3a8004] 2008-03-29 00:15:37 +0000 showing that the fix was released in 8.3.2. Commits on master will usually instead have notes like Branch: master Release: REL8_4_BR [6fc9d4272] 2008-03-29 00:15:28 +0000 showing that this commit is ancestral to release branches 8.4 and later. If no Release: marker appears, the commit hasn't yet made it into any release. 3. Add support for release branches older than 7.4. 4. The implementation is improved by running git log on each branch only back to where the branch sprouts from master. This saves a good deal of time (about 50% of the runtime when generating the complete history). We generate the post-date-mode tags via a direct understanding that they should be applied to master commits made before the branch sprouted, rather than backing into them via matching (which isn't any too reliable when people used identical log messages for successive commits). | <li>Improve git_changelog as per discussion with Robert Haas. 1. Resurrect the behavior where old commits on master will have Branch: labels for branches sprouted after the commit was made. I'm still dubious about this mode, but if you want it, say --post-date or -p. 2. Annotate the Branch: labels with the release or branch in which the commit was publicly released. For example, on a release branch you could see Branch: REL8_3_STABLE Release: REL8_3_2 [92c3a8004] 2008-03-29 00:15:37 +0000 showing that the fix was released in 8.3.2. Commits on master will usually instead have notes like Branch: master Release: REL8_4_BR [6fc9d4272] 2008-03-29 00:15:28 +0000 showing that this commit is ancestral to release branches 8.4 and later. If no Release: marker appears, the commit hasn't yet made it into any release. 3. Add support for release branches older than 7.4. 4. The implementation is improved by running git log on each branch only back to where the branch sprouts from master. This saves a good deal of time (about 50% of the runtime when generating the complete history). We generate the post-date-mode tags via a direct understanding that they should be applied to master commits made before the branch sprouted, rather than backing into them via matching (which isn't any too reliable when people used identical log messages for successive commits). |
| <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=bf429cebd059764198580ca576608921e2022992">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=bf429cebd059764198580ca576608921e2022992</a></li> | <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=bf429cebd059764198580ca576608921e2022992">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=bf429cebd059764198580ca576608921e2022992</a></li> |
| <li>Heikki Linnakangas pushed:</li> | </ul> |
| | <p>Heikki Linnakangas a poussé :</p> |
| | <ul> |
| <li>In src/bin/pg_dump/pg_dump.c, initialize tableoid field correctly when dumping foreign data wrappers and servers. AFAICT it's harmless at the moment because nothing can depend on either, but as soon as we introduce an object type with such dependencies, tableoid needs to be set or pg_dump will fail to interpret the dependencies correctly. In theory, I guess the uninitialized garbage in tableoid could cause the object to be mistaken for some other object with same OID as well. | <li>In src/bin/pg_dump/pg_dump.c, initialize tableoid field correctly when dumping foreign data wrappers and servers. AFAICT it's harmless at the moment because nothing can depend on either, but as soon as we introduce an object type with such dependencies, tableoid needs to be set or pg_dump will fail to interpret the dependencies correctly. In theory, I guess the uninitialized garbage in tableoid could cause the object to be mistaken for some other object with same OID as well. |
| <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=7e8c25c66e9837d5dafeb2b3a0786611226af269">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=7e8c25c66e9837d5dafeb2b3a0786611226af269</a></li> | <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=7e8c25c66e9837d5dafeb2b3a0786611226af269">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=7e8c25c66e9837d5dafeb2b3a0786611226af269</a></li> |
| <li>Alvaro Herrera pushed:</li> | </ul> |
| | <p>Alvaro Herrera a poussé :</p> |
| | <ul> |
| <li>In config/prep_buildtree, prevent doc/src/sgml subdirs from being created, instead of deleting them after the fact. This is a more elegant fix for bug #5595. | <li>In config/prep_buildtree, prevent doc/src/sgml subdirs from being created, instead of deleting them after the fact. This is a more elegant fix for bug #5595. |
| <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=fde5ce4fe2286d3c66cd77db0b7116566ac7b66b">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=fde5ce4fe2286d3c66cd77db0b7116566ac7b66b</a></li> | <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=fde5ce4fe2286d3c66cd77db0b7116566ac7b66b">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=fde5ce4fe2286d3c66cd77db0b7116566ac7b66b</a></li> |
| <li>Peter Eisentraut pushed:</li> | </ul> |
| | <p>Peter Eisentraut a poussé :</p> |
| | <ul> |
| <li>Fix man page markup for <cmdsynopsis> with multiple variants. Command synopses using <cmdsynopsis> with multiple variants previously used <sbr> to break lines between variants. The new man page toolchain introduced in 9.0 makes a mess out of that, and that markup was probably wrong all along, because <sbr> is supposed to break lines within a synopsis, not between them. So fix that by using multiple <cmdsynopsis> elements inside <refsynopsisdiv>. Backpatched to 9.0 | <li>Fix man page markup for <cmdsynopsis> with multiple variants. Command synopses using <cmdsynopsis> with multiple variants previously used <sbr> to break lines between variants. The new man page toolchain introduced in 9.0 makes a mess out of that, and that markup was probably wrong all along, because <sbr> is supposed to break lines within a synopsis, not between them. So fix that by using multiple <cmdsynopsis> elements inside <refsynopsisdiv>. Backpatched to 9.0 |
| <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=635de8365f0299cfa2db24c56abcfccb65d020f0">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=635de8365f0299cfa2db24c56abcfccb65d020f0</a></li> | <a target="_blank" href="http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=635de8365f0299cfa2db24c56abcfccb65d020f0">http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=635de8365f0299cfa2db24c56abcfccb65d020f0</a></li> |
| <p><strong>Correctifs rejetés (à ce jour)</strong></p> | <p><strong>Correctifs rejetés (à ce jour)</strong></p> |
| <ul> | <ul> |
| <li>Pas de déception cette semaine :-)</li> | <li>No one was disappointed this week :-)</li> |
| </ul> | </ul> |
| <p><strong>Correctifs en attente</strong></p> | <p><strong>Correctifs en attente</strong></p> |
