Re: Recovery Test Framework
От | Robert Haas |
---|---|
Тема | Re: Recovery Test Framework |
Дата | |
Msg-id | 603c8f070901120937r617a1a7epfdcef99d58eabea5@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Recovery Test Framework (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Recovery Test Framework
Re: Recovery Test Framework Re: Recovery Test Framework |
Список | pgsql-hackers |
>> 2. Start using more git, as many hackers and committers have already >> started to do. This is the kind of situation where CVS just plain >> falls down because branching and merging are unmanageably difficult in >> it, where in git, they're many-times-a-day operations. > > This is a red herring, unless your proposal also includes making the > master CVS^H^H^Hgit repository world-writable. The complaint I have > about people posting URLs is that there's no stable archive of what the > patches really were, and just because it came out of someone's local git > repository doesn't help that. No, git really does help with this. If Simon were making his changes in git and pushing them to a git branch on git.postgresql.org, you would be able to see exactly what he changed and when he changed it. You would therefore be able to assess whether the changes over the last several months were or were not substantial. The whole point of git is that you don't just publish the master branch - everyone can have their own branches, and they can all be published, and everyone can see the whole development history of every project for whatever purpose they care to see it. git IS a stable archive of what the patches really were. ...Robert
В списке pgsql-hackers по дате отправления: