pg.ddx.io pgsql-committers@postgresql.org mailing list archive
help / color / mirror / Atom feedpgsql: Typo fix.
29+ messages / 9 participants
[nested] [flat]
* pgsql: Typo fix.
@ 2010-04-14 20:17 Robert Haas <rhaas@postgresql.org>
0 siblings, 0 replies; 29+ messages in thread
From: rhaas@postgresql.org @ 2010-04-14 20:17 UTC (permalink / raw)
To: pgsql-committers
Log Message:
-----------
Typo fix. Kevin Grittner.
Modified Files:
--------------
pgsql/src/backend/access/gist:
README (r1.4 -> r1.5)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/gist/README?r1=1.4&r2=1.5)
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix.
@ 2010-12-22 14:33 Robert Haas <rhaas@postgresql.org>
0 siblings, 0 replies; 29+ messages in thread
From: Robert Haas @ 2010-12-22 14:33 UTC (permalink / raw)
To: pgsql-committers
Typo fix.
Noted by Thom Brown.
Branch
------
master
Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=2a0f13a765befefc2658d3729f3e174b7c2...
Modified Files
--------------
doc/src/sgml/ref/pg_ctl-ref.sgml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix
@ 2011-01-11 09:47 Magnus Hagander <magnus@hagander.net>
0 siblings, 0 replies; 29+ messages in thread
From: Magnus Hagander @ 2011-01-11 09:47 UTC (permalink / raw)
To: pgsql-committers
Typo fix
Josh Kupershmidt
Branch
------
master
Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=1c400d330934eb6d70982af522f2bc0458e...
Modified Files
--------------
doc/src/sgml/ref/prepare_transaction.sgml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix
@ 2011-01-11 09:47 Magnus Hagander <magnus@hagander.net>
0 siblings, 0 replies; 29+ messages in thread
From: Magnus Hagander @ 2011-01-11 09:47 UTC (permalink / raw)
To: pgsql-committers
Typo fix
Josh Kupershmidt
Branch
------
REL9_0_STABLE
Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=a1ed4cf6ca6ee2115d9f618ed7930a97842...
Modified Files
--------------
doc/src/sgml/ref/prepare_transaction.sgml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix
@ 2011-02-17 20:57 Bruce Momjian <bruce@momjian.us>
0 siblings, 0 replies; 29+ messages in thread
From: Bruce Momjian @ 2011-02-17 20:57 UTC (permalink / raw)
To: pgsql-committers
Typo fix
Erik Rijkers
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/4f2cfc5bb4c404c24d589339d29c210321f4b4d7
Modified Files
--------------
doc/src/sgml/ecpg.sgml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix.
@ 2011-04-21 02:05 Robert Haas <rhaas@postgresql.org>
0 siblings, 0 replies; 29+ messages in thread
From: Robert Haas @ 2011-04-21 02:05 UTC (permalink / raw)
To: pgsql-committers
Typo fix.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/0babcdf6cfdfb2a828056afc3172ec524f090fd5
Modified Files
--------------
src/backend/commands/tablecmds.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix.
@ 2011-06-02 17:37 Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 29+ messages in thread
From: Tom Lane @ 2011-06-02 17:37 UTC (permalink / raw)
To: pgsql-committers
Typo fix.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/dd2ddfb1cd40393731637101c713a3446cf92144
Modified Files
--------------
src/port/getpeereid.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix.
@ 2011-08-18 17:10 Robert Haas <rhaas@postgresql.org>
0 siblings, 0 replies; 29+ messages in thread
From: Robert Haas @ 2011-08-18 17:10 UTC (permalink / raw)
To: pgsql-committers
Typo fix.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/ffaf9eca4c27d0a63639ffb3022035a297df9900
Modified Files
--------------
contrib/sepgsql/chkselinuxenv | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix.
@ 2011-08-22 16:16 Robert Haas <rhaas@postgresql.org>
0 siblings, 0 replies; 29+ messages in thread
From: Robert Haas @ 2011-08-22 16:16 UTC (permalink / raw)
To: pgsql-committers
Typo fix.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/7488936478cbe2de19a94cb9fbde78e6cd6db947
Modified Files
--------------
src/backend/storage/lmgr/lock.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix.
@ 2012-01-13 13:22 Robert Haas <rhaas@postgresql.org>
0 siblings, 1 reply; 29+ messages in thread
From: Robert Haas @ 2012-01-13 13:22 UTC (permalink / raw)
To: pgsql-committers
Typo fix.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/4d0b11a0ca347e5b0304004625b7eb6752e32ee7
Modified Files
--------------
src/backend/replication/walreceiver.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
^ permalink raw reply [nested|flat] 29+ messages in thread
* Re: pgsql: Typo fix.
@ 2012-01-13 13:29 Simon Riggs <simon@2ndQuadrant.com>
parent: Robert Haas <rhaas@postgresql.org>
0 siblings, 1 reply; 29+ messages in thread
From: Simon Riggs @ 2012-01-13 13:29 UTC (permalink / raw)
To: Robert Haas <rhaas@postgresql.org>; +Cc: pgsql-committers
On Fri, Jan 13, 2012 at 1:22 PM, Robert Haas <rhaas@postgresql.org> wrote:
> Typo fix.
Hmm, how strange. I fixed that bug immediately before commit, so must
have skipped a step while committing.
Thanks.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
^ permalink raw reply [nested|flat] 29+ messages in thread
* Re: pgsql: Typo fix.
@ 2012-01-13 13:39 Dave Page <dpage@pgadmin.org>
parent: Simon Riggs <simon@2ndQuadrant.com>
0 siblings, 1 reply; 29+ messages in thread
From: Dave Page @ 2012-01-13 13:39 UTC (permalink / raw)
To: Simon Riggs <simon@2ndquadrant.com>; +Cc: Robert Haas <rhaas@postgresql.org>; pgsql-committers
On Fri, Jan 13, 2012 at 1:29 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On Fri, Jan 13, 2012 at 1:22 PM, Robert Haas <rhaas@postgresql.org> wrote:
>
>> Typo fix.
>
> Hmm, how strange. I fixed that bug immediately before commit, so must
> have skipped a step while committing.
If you modify a file after git-adding it, you have to re-add it before
committing. Possible cause?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
^ permalink raw reply [nested|flat] 29+ messages in thread
* Re: pgsql: Typo fix.
@ 2012-01-13 14:03 Simon Riggs <simon@2ndQuadrant.com>
parent: Dave Page <dpage@pgadmin.org>
0 siblings, 2 replies; 29+ messages in thread
From: Simon Riggs @ 2012-01-13 14:03 UTC (permalink / raw)
To: Dave Page <dpage@pgadmin.org>; +Cc: Robert Haas <rhaas@postgresql.org>; pgsql-committers
On Fri, Jan 13, 2012 at 1:39 PM, Dave Page <dpage@pgadmin.org> wrote:
> On Fri, Jan 13, 2012 at 1:29 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> On Fri, Jan 13, 2012 at 1:22 PM, Robert Haas <rhaas@postgresql.org> wrote:
>>
>>> Typo fix.
>>
>> Hmm, how strange. I fixed that bug immediately before commit, so must
>> have skipped a step while committing.
>
> If you modify a file after git-adding it, you have to re-add it before
> committing. Possible cause?
No, dumber than that.
I compiled a new version, just skipped the bit where I updated the new
patch version, so the old one just got applied.
I keep separate dev and write repositories and use patches to move
between them. Which gives me less chance of committing dev code
accidentally (like I just did). Is there a better way?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
^ permalink raw reply [nested|flat] 29+ messages in thread
* Re: pgsql: Typo fix.
@ 2012-01-13 14:08 Dave Page <dpage@pgadmin.org>
parent: Simon Riggs <simon@2ndQuadrant.com>
1 sibling, 0 replies; 29+ messages in thread
From: Dave Page @ 2012-01-13 14:08 UTC (permalink / raw)
To: Simon Riggs <simon@2ndquadrant.com>; +Cc: Robert Haas <rhaas@postgresql.org>; pgsql-committers
On Fri, Jan 13, 2012 at 2:03 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On Fri, Jan 13, 2012 at 1:39 PM, Dave Page <dpage@pgadmin.org> wrote:
>> On Fri, Jan 13, 2012 at 1:29 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>>> On Fri, Jan 13, 2012 at 1:22 PM, Robert Haas <rhaas@postgresql.org> wrote:
>>>
>>>> Typo fix.
>>>
>>> Hmm, how strange. I fixed that bug immediately before commit, so must
>>> have skipped a step while committing.
>>
>> If you modify a file after git-adding it, you have to re-add it before
>> committing. Possible cause?
>
> No, dumber than that.
>
> I compiled a new version, just skipped the bit where I updated the new
> patch version, so the old one just got applied.
>
> I keep separate dev and write repositories and use patches to move
> between them. Which gives me less chance of committing dev code
> accidentally (like I just did). Is there a better way?
I suspect the git purists will suggest using a private branch to
develop in and then merging (and squashing) that into the master
branch to be pushed. I do that for some projects, and a similar
workflow to yours for others. Git gives you 20 ways to do anything
though, so I'm sure there are other options.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
^ permalink raw reply [nested|flat] 29+ messages in thread
* Re: pgsql: Typo fix.
@ 2012-01-13 14:26 Magnus Hagander <magnus@hagander.net>
parent: Simon Riggs <simon@2ndQuadrant.com>
1 sibling, 1 reply; 29+ messages in thread
From: Magnus Hagander @ 2012-01-13 14:26 UTC (permalink / raw)
To: Simon Riggs <simon@2ndquadrant.com>; +Cc: Dave Page <dpage@pgadmin.org>; Robert Haas <rhaas@postgresql.org>; pgsql-committers
On Fri, Jan 13, 2012 at 15:03, Simon Riggs <simon@2ndquadrant.com> wrote:
> On Fri, Jan 13, 2012 at 1:39 PM, Dave Page <dpage@pgadmin.org> wrote:
>> On Fri, Jan 13, 2012 at 1:29 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>>> On Fri, Jan 13, 2012 at 1:22 PM, Robert Haas <rhaas@postgresql.org> wrote:
>>>
>>>> Typo fix.
>>>
>>> Hmm, how strange. I fixed that bug immediately before commit, so must
>>> have skipped a step while committing.
>>
>> If you modify a file after git-adding it, you have to re-add it before
>> committing. Possible cause?
>
> No, dumber than that.
>
> I compiled a new version, just skipped the bit where I updated the new
> patch version, so the old one just got applied.
>
> I keep separate dev and write repositories and use patches to move
> between them. Which gives me less chance of committing dev code
> accidentally (like I just did). Is there a better way?
Just FWIW, I use a separate development repository as well. But I have
it added as a remote from the "commit repository", and thus just do a
"git merge --squash" instead of manually moving them with "patch".
But I am very much a fan of keeping the repos separate for just that
reason - don't want to accidentally commit dev code.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
^ permalink raw reply [nested|flat] 29+ messages in thread
* Re: pgsql: Typo fix.
@ 2012-01-13 15:22 Simon Riggs <simon@2ndQuadrant.com>
parent: Magnus Hagander <magnus@hagander.net>
0 siblings, 1 reply; 29+ messages in thread
From: Simon Riggs @ 2012-01-13 15:22 UTC (permalink / raw)
To: Magnus Hagander <magnus@hagander.net>; +Cc: Dave Page <dpage@pgadmin.org>; Robert Haas <rhaas@postgresql.org>; pgsql-committers
On Fri, Jan 13, 2012 at 2:26 PM, Magnus Hagander <magnus@hagander.net> wrote:
> Just FWIW, I use a separate development repository as well. But I have
> it added as a remote from the "commit repository", and thus just do a
> "git merge --squash" instead of manually moving them with "patch".
>
> But I am very much a fan of keeping the repos separate for just that
> reason - don't want to accidentally commit dev code.
OK thanks.
My patch foo seems occasionally faulty, but git merge --disaster is
something I'm happy to avoid. I'll work on my hand grenade juggling
skills before I do that.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
^ permalink raw reply [nested|flat] 29+ messages in thread
* Re: pgsql: Typo fix.
@ 2012-01-13 15:49 Andrew Dunstan <andrew@dunslane.net>
parent: Simon Riggs <simon@2ndQuadrant.com>
0 siblings, 1 reply; 29+ messages in thread
From: Andrew Dunstan @ 2012-01-13 15:49 UTC (permalink / raw)
To: Simon Riggs <simon@2ndQuadrant.com>; +Cc: Magnus Hagander <magnus@hagander.net>; Dave Page <dpage@pgadmin.org>; Robert Haas <rhaas@postgresql.org>; pgsql-committers
On 01/13/2012 10:22 AM, Simon Riggs wrote:
> On Fri, Jan 13, 2012 at 2:26 PM, Magnus Hagander<magnus@hagander.net> wrote:
>
>> Just FWIW, I use a separate development repository as well. But I have
>> it added as a remote from the "commit repository", and thus just do a
>> "git merge --squash" instead of manually moving them with "patch".
>>
>> But I am very much a fan of keeping the repos separate for just that
>> reason - don't want to accidentally commit dev code.
> OK thanks.
>
> My patch foo seems occasionally faulty, but git merge --disaster is
> something I'm happy to avoid. I'll work on my hand grenade juggling
> skills before I do that.
How you work is up to you, but "git merge --squash" is pretty safe,
since it doesn't actually commit anything.
cheers
andrew
^ permalink raw reply [nested|flat] 29+ messages in thread
* Re: pgsql: Typo fix.
@ 2012-01-13 16:05 Alvaro Herrera <alvherre@commandprompt.com>
parent: Andrew Dunstan <andrew@dunslane.net>
0 siblings, 2 replies; 29+ messages in thread
From: Alvaro Herrera @ 2012-01-13 16:05 UTC (permalink / raw)
To: Andrew Dunstan <andrew@dunslane.net>; +Cc: Simon Riggs <simon@2ndquadrant.com>; Magnus Hagander <magnus@hagander.net>; Dave Page <dpage@pgadmin.org>; Robert Haas <rhaas@postgresql.org>; pgsql-committers
Excerpts from Andrew Dunstan's message of vie ene 13 12:49:58 -0300 2012:
>
> On 01/13/2012 10:22 AM, Simon Riggs wrote:
> > On Fri, Jan 13, 2012 at 2:26 PM, Magnus Hagander<magnus@hagander.net> wrote:
> >
> >> Just FWIW, I use a separate development repository as well. But I have
> >> it added as a remote from the "commit repository", and thus just do a
> >> "git merge --squash" instead of manually moving them with "patch".
> >>
> >> But I am very much a fan of keeping the repos separate for just that
> >> reason - don't want to accidentally commit dev code.
> > OK thanks.
> >
> > My patch foo seems occasionally faulty, but git merge --disaster is
> > something I'm happy to avoid. I'll work on my hand grenade juggling
> > skills before I do that.
>
>
> How you work is up to you, but "git merge --squash" is pretty safe,
> since it doesn't actually commit anything.
And if things go wrong you can always do git merge --abort.
I, too, used to be scared of some of the options that git gives us, but
after experimentation I found some of them to be hugely useful and safe
enough that I now very rarely run use patches anymore.
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
^ permalink raw reply [nested|flat] 29+ messages in thread
* Re: pgsql: Typo fix.
@ 2012-01-13 16:48 Simon Riggs <simon@2ndQuadrant.com>
parent: Alvaro Herrera <alvherre@commandprompt.com>
1 sibling, 0 replies; 29+ messages in thread
From: Simon Riggs @ 2012-01-13 16:48 UTC (permalink / raw)
To: Alvaro Herrera <alvherre@commandprompt.com>; +Cc: Andrew Dunstan <andrew@dunslane.net>; Magnus Hagander <magnus@hagander.net>; Dave Page <dpage@pgadmin.org>; Robert Haas <rhaas@postgresql.org>; pgsql-committers
On Fri, Jan 13, 2012 at 4:05 PM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
>> How you work is up to you, but "git merge --squash" is pretty safe,
>> since it doesn't actually commit anything.
>
> And if things go wrong you can always do git merge --abort.
>
> I, too, used to be scared of some of the options that git gives us, but
> after experimentation I found some of them to be hugely useful and safe
> enough that I now very rarely run use patches anymore.
Gets better and better - very positive. OK, will give it a try. Thanks guys.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
^ permalink raw reply [nested|flat] 29+ messages in thread
* Re: pgsql: Typo fix.
@ 2012-01-13 17:29 Andrew Dunstan <andrew@dunslane.net>
parent: Alvaro Herrera <alvherre@commandprompt.com>
1 sibling, 1 reply; 29+ messages in thread
From: Andrew Dunstan @ 2012-01-13 17:29 UTC (permalink / raw)
To: Alvaro Herrera <alvherre@commandprompt.com>; +Cc: Simon Riggs <simon@2ndquadrant.com>; Magnus Hagander <magnus@hagander.net>; Dave Page <dpage@pgadmin.org>; Robert Haas <rhaas@postgresql.org>; pgsql-committers
On 01/13/2012 11:05 AM, Alvaro Herrera wrote:
> Excerpts from Andrew Dunstan's message of vie ene 13 12:49:58 -0300 2012:
>> On 01/13/2012 10:22 AM, Simon Riggs wrote:
>>> On Fri, Jan 13, 2012 at 2:26 PM, Magnus Hagander<magnus@hagander.net> wrote:
>>>
>>>> Just FWIW, I use a separate development repository as well. But I have
>>>> it added as a remote from the "commit repository", and thus just do a
>>>> "git merge --squash" instead of manually moving them with "patch".
>>>>
>>>> But I am very much a fan of keeping the repos separate for just that
>>>> reason - don't want to accidentally commit dev code.
>>> OK thanks.
>>>
>>> My patch foo seems occasionally faulty, but git merge --disaster is
>>> something I'm happy to avoid. I'll work on my hand grenade juggling
>>> skills before I do that.
>>
>> How you work is up to you, but "git merge --squash" is pretty safe,
>> since it doesn't actually commit anything.
> And if things go wrong you can always do git merge --abort.
>
> I, too, used to be scared of some of the options that git gives us, but
> after experimentation I found some of them to be hugely useful and safe
> enough that I now very rarely run use patches anymore.
Yeah. Just note this from the docs:
The third syntax ("git merge --abort") can only be run after the
merge has resulted in conflicts. git merge --abort will abort the
merge process and try to reconstruct the
pre-merge state. However, if there were uncommitted changes when the
merge started (and especially if those changes were further modified
after the merge was started), git merge
--abort will in some cases be unable to reconstruct the original
(pre-merge) changes. Therefore:
Warning: Running git merge with uncommitted changes is discouraged:
while possible, it leaves you in a state that is hard to back out of
in the case of a conflict.
Of course, if you aren't doing dev work on the tree in question that
shouldn't apply, presumably.
cheers
andrew
^ permalink raw reply [nested|flat] 29+ messages in thread
* Re: pgsql: Typo fix.
@ 2012-01-13 18:46 Alvaro Herrera <alvherre@commandprompt.com>
parent: Andrew Dunstan <andrew@dunslane.net>
0 siblings, 0 replies; 29+ messages in thread
From: Alvaro Herrera @ 2012-01-13 18:46 UTC (permalink / raw)
To: Andrew Dunstan <andrew@dunslane.net>; +Cc: Simon Riggs <simon@2ndquadrant.com>; Magnus Hagander <magnus@hagander.net>; Dave Page <dpage@pgadmin.org>; Robert Haas <rhaas@postgresql.org>; pgsql-committers
Excerpts from Andrew Dunstan's message of vie ene 13 14:29:44 -0300 2012:
> Yeah. Just note this from the docs:
>
> The third syntax ("git merge --abort") can only be run after the
> merge has resulted in conflicts. git merge --abort will abort the
> merge process and try to reconstruct the
> pre-merge state. However, if there were uncommitted changes when the
> merge started (and especially if those changes were further modified
> after the merge was started), git merge
> --abort will in some cases be unable to reconstruct the original
> (pre-merge) changes.
Hm. Whenever I find myself trying to merge something in a tree that
also has uncommitted changes (which is not very often), what I do is
"git stash" to save my work elsewhere and then run the git merge. That
way, if things go wrong (which is also not very often), I can just abort
the merge and pop the patch from the stash, and I'm right back where I
started. Otherwise, I pop my patch from the stash anyway and any merges
are handled by the same merge mechanism, so I can also roll that back if
things don't turn the way I initially wanted.
So while you can certainly screw up and lose work, it's also true that
you have all the tools not to.
--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix
@ 2012-01-22 21:34 Magnus Hagander <magnus@hagander.net>
0 siblings, 0 replies; 29+ messages in thread
From: Magnus Hagander @ 2012-01-22 21:34 UTC (permalink / raw)
To: pgsql-committers
Typo fix
Guillaume Lelarge
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/4993a49b7cf1d23dfe1f9e1a85d9411b8ff57454
Modified Files
--------------
doc/src/sgml/tcn.sgml | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix.
@ 2012-03-06 13:24 Robert Haas <rhaas@postgresql.org>
0 siblings, 0 replies; 29+ messages in thread
From: Robert Haas @ 2012-03-06 13:24 UTC (permalink / raw)
To: pgsql-committers
Typo fix.
Fujii Masao
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/bc97c38115ed48c1dd27e9d534faae204427f9a5
Modified Files
--------------
src/backend/access/transam/xlog.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix.
@ 2013-09-18 13:01 Robert Haas <rhaas@postgresql.org>
0 siblings, 0 replies; 29+ messages in thread
From: Robert Haas @ 2013-09-18 13:01 UTC (permalink / raw)
To: pgsql-committers
Typo fix.
Etsuro Fujita
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/86a174bff0730791c5c262d646d4fe28c2485be1
Modified Files
--------------
src/backend/access/spgist/spgtextproc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix.
@ 2015-01-19 16:43 Robert Haas <rhaas@postgresql.org>
0 siblings, 0 replies; 29+ messages in thread
From: Robert Haas @ 2015-01-19 16:43 UTC (permalink / raw)
To: pgsql-committers
Typo fix.
Etsuro Fujita
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/1605291b6c14be92915948d17f5509191632c97f
Modified Files
--------------
src/backend/executor/execMain.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix.
@ 2016-03-19 18:37 Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 29+ messages in thread
From: Tom Lane @ 2016-03-19 18:37 UTC (permalink / raw)
To: pgsql-committers
Typo fix.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/78e7c4439917b01afd645a2ec657008ba6c33d37
Modified Files
--------------
src/interfaces/ecpg/preproc/pgc.l | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix.
@ 2016-07-03 22:43 Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 29+ messages in thread
From: Tom Lane @ 2016-07-03 22:43 UTC (permalink / raw)
To: pgsql-committers
Typo fix.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/29a2195de645759d66ee7e77c4c05b2c4aeb6729
Modified Files
--------------
src/backend/optimizer/path/allpaths.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix
@ 2024-07-08 13:16 Amit Langote <amitlan@postgresql.org>
0 siblings, 0 replies; 29+ messages in thread
From: Amit Langote @ 2024-07-08 13:16 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Typo fix
Reported-by: Junwang Zhao <zhjwpku@gmail.com>
Discussion: https://postgr.es/m/CAEG8a3KPi=LayiTwJ11ikF7bcqnZUrcj8NgX0V8nO1mQKZ9GfQ@mail.gmail.com
Backpatch-through: 17
Branch
------
REL_17_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/d4f8517b0b9436fa3478851024870d8ee0b67801
Modified Files
--------------
src/common/jsonapi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 29+ messages in thread
* pgsql: Typo fix
@ 2024-07-08 13:16 Amit Langote <amitlan@postgresql.org>
0 siblings, 0 replies; 29+ messages in thread
From: Amit Langote @ 2024-07-08 13:16 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Typo fix
Reported-by: Junwang Zhao <zhjwpku@gmail.com>
Discussion: https://postgr.es/m/CAEG8a3KPi=LayiTwJ11ikF7bcqnZUrcj8NgX0V8nO1mQKZ9GfQ@mail.gmail.com
Backpatch-through: 17
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/519d710720159046c90c08095e70fdb486d38053
Modified Files
--------------
src/common/jsonapi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
^ permalink raw reply [nested|flat] 29+ messages in thread
end of thread, other threads:[~2024-07-08 13:16 UTC | newest]
Thread overview: 29+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2010-04-14 20:17 pgsql: Typo fix. Robert Haas <rhaas@postgresql.org>
2010-12-22 14:33 pgsql: Typo fix. Robert Haas <rhaas@postgresql.org>
2011-01-11 09:47 pgsql: Typo fix Magnus Hagander <magnus@hagander.net>
2011-01-11 09:47 pgsql: Typo fix Magnus Hagander <magnus@hagander.net>
2011-02-17 20:57 pgsql: Typo fix Bruce Momjian <bruce@momjian.us>
2011-04-21 02:05 pgsql: Typo fix. Robert Haas <rhaas@postgresql.org>
2011-06-02 17:37 pgsql: Typo fix. Tom Lane <tgl@sss.pgh.pa.us>
2011-08-18 17:10 pgsql: Typo fix. Robert Haas <rhaas@postgresql.org>
2011-08-22 16:16 pgsql: Typo fix. Robert Haas <rhaas@postgresql.org>
2012-01-13 13:22 pgsql: Typo fix. Robert Haas <rhaas@postgresql.org>
2012-01-13 13:29 ` Simon Riggs <simon@2ndQuadrant.com>
2012-01-13 13:39 ` Dave Page <dpage@pgadmin.org>
2012-01-13 14:03 ` Simon Riggs <simon@2ndQuadrant.com>
2012-01-13 14:08 ` Dave Page <dpage@pgadmin.org>
2012-01-13 14:26 ` Magnus Hagander <magnus@hagander.net>
2012-01-13 15:22 ` Simon Riggs <simon@2ndQuadrant.com>
2012-01-13 15:49 ` Andrew Dunstan <andrew@dunslane.net>
2012-01-13 16:05 ` Alvaro Herrera <alvherre@commandprompt.com>
2012-01-13 16:48 ` Simon Riggs <simon@2ndQuadrant.com>
2012-01-13 17:29 ` Andrew Dunstan <andrew@dunslane.net>
2012-01-13 18:46 ` Alvaro Herrera <alvherre@commandprompt.com>
2012-01-22 21:34 pgsql: Typo fix Magnus Hagander <magnus@hagander.net>
2012-03-06 13:24 pgsql: Typo fix. Robert Haas <rhaas@postgresql.org>
2013-09-18 13:01 pgsql: Typo fix. Robert Haas <rhaas@postgresql.org>
2015-01-19 16:43 pgsql: Typo fix. Robert Haas <rhaas@postgresql.org>
2016-03-19 18:37 pgsql: Typo fix. Tom Lane <tgl@sss.pgh.pa.us>
2016-07-03 22:43 pgsql: Typo fix. Tom Lane <tgl@sss.pgh.pa.us>
2024-07-08 13:16 pgsql: Typo fix Amit Langote <amitlan@postgresql.org>
2024-07-08 13:16 pgsql: Typo fix Amit Langote <amitlan@postgresql.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox