| From: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Marko Kreen <markokr(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>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, 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 19:33:35 |
| Message-ID: | 4A26D00F.8000403@cheapcomplexdevices.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> But I
> wonder if it would make more sense to include some kind of metadata in
> the commit message (or some other property of the commit? does git
> support that?) to make it not depend on that.
From elsewhere in this thread[1], 'The "git cherry-pick" ... "-x" flag adds
a note to the commit comment describing the relationship between the commits.'
If the commit on the main branch had this message
=================
added a line on the main branch
=================
The commit on the cherry picked branch will have this comment
=================
added a line on the main branch
(cherry picked from commit 189ef03b4f4ed5078328f7965c7bfecce318490d)
=================
where the big hex string identifies the comment on the other branch.
[1] http://archives.postgresql.org/pgsql-hackers/2009-06/msg00191.php
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aidan Van Dyk | 2009-06-03 19:53:48 | Re: Managing multiple branches in git |
| Previous Message | Tom Lane | 2009-06-03 19:24:13 | Re: Plan time Improvement - 64bit bitmapset |