Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Typo fix.

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Dave Page <dpage(at)pgadmin(dot)org>, Robert Haas <rhaas(at)postgresql(dot)org>, Pg Committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Typo fix.
Date: 2012-01-13 16:48:48
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
On Fri, Jan 13, 2012 at 4:05 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)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         
 PostgreSQL Development, 24x7 Support, Training & Services

In response to

pgsql-committers by date

Next:From: Andrew DunstanDate: 2012-01-13 17:29:44
Subject: Re: pgsql: Typo fix.
Previous:From: Alvaro HerreraDate: 2012-01-13 16:05:51
Subject: Re: pgsql: Typo fix.

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group