| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: git author vs committer |
| Date: | 2012-09-12 14:48:09 |
| Message-ID: | 1347461226-sup-7608@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Peter Eisentraut's message of mié sep 12 11:21:36 -0300 2012:
> A while ago I wanted to cherry-pick a patch from master to a back-branch
> that was initially committed by someone else. That was rejected because
> our git server requires author==committer. I don't think that
> restriction is particularly useful and should be lifted. I'm not saying
> we should let anyone be an author, but within the pool of committers, I
> think we should let the mechanics of the git tools determine these
> fields.
+1. I had the same problem.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Crawford | 2012-09-12 15:25:10 | Re: 9.2 bug? "variable not found in subplan target list" |
| Previous Message | Louis-David Mitterrand | 2012-09-12 14:36:34 | 9.2 bug? "variable not found in subplan target list" |