Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.
От | Tom Lane |
---|---|
Тема | Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog. |
Дата | |
Msg-id | 26853.1285517318@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog. (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: [COMMITTERS] pgsql: Still more tweaking of git_changelog.
|
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > On Sun, Sep 26, 2010 at 1:51 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Still more tweaking of git_changelog. > Uhm, could you stop massively changing the behavior of this script > with no discussion at all? Uh, there was no discussion of the original behavior of the script either. > I happen to think that this is a > distinctly bad idea. It defeats one of the major use cases of the > original script, which is being able to easily figure out which > branches a certain commit is in. Hm? As far as I can tell, this fixes that not breaks it. The problem I was seeing was that commits would be attributed to a branch when in fact they were made before the branch ever existed. > If you want to have an option for > this behavior, fine, but please do not presume that everyone wants the > same thing as you (since that is evidently not the case) or that you > are the only person who is using it (if that were so, it should be > stored in your personal workspace, rather than our community > repository). I was under the impression that the purpose of the script was to replace cvs2cl and do approximately what cvs2cl did. If you have another use-case then please explain what it is and why this change is bad for it. regards, tom lane
В списке pgsql-hackers по дате отправления: