| From: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
|---|---|
| To: | Marko Kreen <markokr(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Stark <stark(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Markus Wanner <markus(at)bluegap(dot)ch>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL Developer meeting minutes up |
| Date: | 2009-06-03 15:52:49 |
| Message-ID: | 20090603155249.GO23972@yugib.highrise.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Marko Kreen <markokr(at)gmail(dot)com> [090603 11:28]:
> I'm not certain, but I remember using cherry pick and seeing
> several commits in result. This seems to be a point that needs
> to be checked.
I'm not sure what you're recalling, but git cherry-pick takes a single
commit, and applies it as a single commit (or, with -n, doesn't actually
commit it). That's what it does... There are various *other* tools (like
rebase, am, cherry, etc) which operate on "sets" of commits.
--
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-06-03 16:01:48 | Re: Managing multiple branches in git |
| Previous Message | Andres Freund | 2009-06-03 15:48:02 | Plan time Improvement - 64bit bitmapset |