From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Aidan Van Dyk" <aidan(at)highrise(dot)ca> |
Cc: | "Tatsuo Ishii" <ishii(at)postgresql(dot)org>, <andrew(at)dunslane(dot)net>, <david(at)fetter(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WITH RECURSIVE patches V0.1 TODO items |
Date: | 2008-05-27 14:02:23 |
Message-ID: | 871w3nlua8.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Aidan Van Dyk" <aidan(at)highrise(dot)ca> writes:
> Something like this is easily done in GIT as well:
> git fetch ## Fetch any new commits done in the origin to the local repo
> git merge origin/master ## or any other branch you want..
> git push ## publish your work for others to fetch
I would very much like to start using GIT to do this. The main difference is
that when a contributor wants to merge back the changes from upstream GIT
knows which changes upstream correspond to the commits the contributor made.
So it can avoid a lot of conflicts when the upstream version has subsequent
changes to the same areas.
The end result is also a lot cleaner. Instead of a lot of commit messages that
just say "applying patch from Foo" all the original separate commits can be
preserved.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2008-05-27 14:11:01 | Re: WITH RECURSIVE patches V0.1 TODO items |
Previous Message | Aidan Van Dyk | 2008-05-27 13:45:48 | Re: WITH RECURSIVE patches V0.1 TODO items |