From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Markus Schiltknecht <markus(at)bluegap(dot)ch>, Richard Levitte - VMS Whacker <richard(at)levitte(dot)org>, tgl(at)sss(dot)pgh(dot)pa(dot)us, monotone-devel(at)nongnu(dot)org, wt(at)penguintechs(dot)org, stark(at)enterprisedb(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [Monotone-devel] Re: SCMS question |
Date: | 2007-02-22 17:49:53 |
Message-ID: | 20070222174953.GJ4276@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan wrote:
> It's also fair to say that this is a subject about which we usually get
> much more noise from partisans of other SCM systems than from the
> relatively small number of people who actually have to maintain the
> postgresql code. (As Tom has pointed out, our biggest pain point is the
> occasional wish to move things across directories.)
There are more features we are missing -- we just don't know about them
:-)
For example, currently if I have a patch and somebody reviews it and
opines that I have to change foo to bar; then I resubmit the patch. How
do they find out whether I actually changed foo to bar? Currently there
are two alternatives:
1. trust that I did it
2. review the whole patch again
With a distributed SCM, I could just patch the code and commit a new
revision in my branch to just change foo to bar, and then the reviewer
can check that I truly did what he wanted.
Another easy thing to do is to track the current HEAD in a branch of
mine. Keeping patches up to date in parallel with other developments is
easier.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2007-02-22 17:50:24 | Re: tsearch in core patch, for inclusion |
Previous Message | Pavel Stehule | 2007-02-22 17:45:28 | Re: tsearch in core patch, for inclusion |