Re: Multi-branch committing in git, revisited - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Multi-branch committing in git, revisited
Date
Msg-id 889B5864-F5ED-4B7D-8A1E-1AC710B2A177@kineticode.com
Whole thread Raw
In response to Re: Multi-branch committing in git, revisited  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sep 21, 2010, at 8:19 PM, Tom Lane wrote:

> You sure about the "staged" part?

Yes, I do it all the time (I make a lot of mistakes).

> Offhand I think I like Andrew's recommendation of a shortlived branch
> better.  In essence your idea is using the tip of "master" itself as a
> shortlived branch, which is maybe a bit too cute.  If you get distracted
> and need to do something else for awhile, the tip of "master" is not
> where you want your not-yet-pushable work to be.

Yes, I think using branches for everything is generally the way to go. But if you wanted to just use your existing
approach,then reset --soft HEAD^ would work, too. 

Best,

David




pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: wip: functions median and percentile
Next
From: Peter Eisentraut
Date:
Subject: Re: psql's \dn versus temp schemas