Re: Report: removing the inconsistencies in our CVS->git conversion
Tom Lane <tgl@sss.pgh.pa.us>
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Applied patch to jdbc from Kim Ho at RedHat, fixing improper handling of empty queries under the V3 protocol
- e8839c2b6c00 7.4.1 cited
-
Applied patch for jdbc from Kim Ho at RedHat to more correctly deal with boolean values
- c020d67bc692 7.4.1 cited
-
Applied patch from Oliver Jowett to improve a buffer sizing.
- d7c609f7c4de 7.4.1 cited
-
Code cleanup inspired by recent resname bug report (doesn't fix the bug
- 88381ade63de 7.4.1 cited
-
Pass shared memory id and socket descriptor number on command line for
- d9fd7d12f6c0 7.4.1 cited
-
Second try at avoiding conflicts with system isblank().
- e3859d1ad982 7.2.5 cited
-
Applied Kris Jurkas patch to fix rollback and SQLException
- 985e551b4866 7.4.1 cited
-
applied patch from Oliver Jowett
- d23fd9572b4c 7.4.1 cited
-
Make the world at least somewhat safe for zero-column tables, and
- 6d0d15c45173 7.3.1 cited
-
Add mention of -F not supported by pg_dumpall. Code already disallows it.
- c43760a7143b 7.3.1 cited
-
Two versions of QueryExecutor, currently only version 2 works 100%
- 78d40a2a2f41 7.3.1 cited
-
modifications to the way the protocol is handled to be consistent with
- 54cc549d8f25 7.3.1 cited
-
Part of Anders Bengtsson's patch to clean up Connection.java
- 00923229c2f0 7.3.1 cited
-
Applied Anders patch to move the startup code out of Connection into StartupPacket
- d96c29ab301a 7.3.1 cited
-
>Added ServerEncoding
- eb1fb8650fb2 7.3.1 cited
-
> I am backing out this patch. Please resubmit with this corrected. Thanks.
- d3337c6e3f9b 7.3.1 cited
-
Fixes bug where query hangs if there is an error in the query, went back to
- 202a19e47bfd 7.3.1 cited
-
Backpatch array I/O code and documentation fixes, also array slice
- bbc1fb07c625 7.2.1 cited
-
fixed QueryExecuter to deal with multiple errors
- 134fe5ec61cb 7.3.1 cited
-
Repair bad calculation in timetz_izone() which gave erroneous results.
- efec53adb3a3 7.2.1 cited
-
backed out changes for cancel, no need to look for two 'Z' responses
- ffe356b5dd39 7.3.1 cited
-
Patch by Nicolas Verger to correctly propogate SQLWarning to the Statement and ResultSet
- 29ea8ff9b13f 7.3.1 cited
-
fixed cancel query bug introduced by patch
- ff2f9b663f73 7.3.1 cited
-
Autoconf for jdbc debug changes.
- b7cc409f7f5e 7.3.1 cited
-
Updated the list of encodings supported to match what the backend now supports
- bf737b859f7e 7.2.1 cited
-
Added some additional comments in the code
- f50793c743c7 7.2.1 cited
-
Update TODO list.
- 311eef41ea01 7.2.1 cited
-
Remove ConnectionHook.java. No longer used, bad code.
- 5621ec0629b1 7.2.1 cited
-
The attached patch removes some old and dead code (and some related
- 0e4d43f4593c 7.2.1 cited
-
First batch of the tools merged in...
- e2e84a1c5e13 7.1.1 cited
-
This patch fixes an arrayindexoutofbounds exception that was just
- 4e45005ffb8f 7.1.1 cited
-
Add ./include/config.h.win32 to RELEASE update list.
- ba6fda5191a1 7.1.1 cited
I wrote: > In addition to the above, we're going to want to clean up the > Release_2_0_0 and Release_2_0 tags, but I'm not sure if there's > a reasonable way to script those when the commit SHA1's aren't frozen > yet. I can give you timestamps for the commits they should point at, > but I lack the git-fu to convert that into a git tag command. > Similarly, we're going to want to repoint REL6_5, REL7_1, REL7_1_2 > tags at more appropriate places, but right now all I have for those is > timestamps. (I've also identified places to tag the other early > releases, but those tags can certainly be added later.) Actually, the simplest way to handle this might be to just delete all five of those tags during the conversion, and then I'll put them back in the right places later when I add the other old-release tags. That way we won't have any tags getting moved after the repository is published. (Or am I wrong about that being something to avoid? But in any case we want to gc the manufactured commits for Release_2_0_0 and Release_2_0.) regards, tom lane