From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Abhijit Menon-Sen" <ams(at)oryx(dot)com> |
Cc: | "David Fetter" <david(at)fetter(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WITH RECURSIVE updated to CVS TIP |
Date: | 2008-07-10 10:52:43 |
Message-ID: | 87zloqc8p0.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
"Abhijit Menon-Sen" <ams(at)oryx(dot)com> writes:
> The only real benefit to review that I can imagine would be if full
> change history were available, which it could do if a) changes were
> committed separately with proper comments and b) if the branch were
> *NOT* rebased, but instead periodically merged with origin/master.
>
> That way I could pull from the repository and run e.g.
> "git-log --stat origin/master..with-recursive" or similar.
Additionally if other people could commit change patches to the repository or
submit patches which upstream could apply then git would be able to update
submitters trees with just the patches they're missing (ie, skipping the
patches they submitted upstream or merging them cleanly)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training!
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Kreen | 2008-07-10 11:56:31 | Re: Follow-up on replication hooks for PostgreSQL |
Previous Message | Abhijit Menon-Sen | 2008-07-10 10:42:34 | Re: WITH RECURSIVE updated to CVS TIP |
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Kreen | 2008-07-10 12:10:39 | Re: review: table function support |
Previous Message | Abhijit Menon-Sen | 2008-07-10 10:42:34 | Re: WITH RECURSIVE updated to CVS TIP |