| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Mark Cave-Ayland <mark(dot)cave-ayland(at)ilande(dot)co(dot)uk>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Joe Conway <mail(at)joeconway(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: Commitfest problems |
| Date: | 2014-12-20 05:15:04 |
| Message-ID: | 20141220051504.GL5023@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-12-19 22:17:54 -0600, Jim Nasby wrote:
> git does allow you to revise a commit message; it just makes
> downstream pulls uglier if the commit was already pushed (see
> https://help.github.com/articles/changing-a-commit-message/) It might
> be possible to minimize or even eliminate that pain via git hooks.
That's completely not acceptable for anything used by others.
What can sanely changed after the fact is 'git notes'. With that notes
to commits can be added, edited and changed after the original
commit.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-12-20 05:15:42 | Re: hash_create API changes (was Re: speedup tidbitmap patch: hash BlockNumber) |
| Previous Message | Jim Nasby | 2014-12-20 04:17:54 | Re: Commitfest problems |