Re: pgindent-polluted commits
От | Tom Lane |
---|---|
Тема | Re: pgindent-polluted commits |
Дата | |
Msg-id | 1888.1452705191@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: pgindent-polluted commits (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: pgindent-polluted commits
Re: pgindent-polluted commits Re: pgindent-polluted commits Re: pgindent-polluted commits |
Список | pgsql-hackers |
Simon Riggs <simon@2ndQuadrant.com> writes: > On 13 January 2016 at 14:48, Noah Misch <noah@leadboat.com> wrote: >> I've noticed commits, from a few of you, carrying pgindent changes to lines >> the patch would not otherwise change. > Could we review again why this matters? Basically this is trading off convenience of the committer (all of the alternatives Noah mentions are somewhat annoying) versus the convenience of post-commit reviewers. I'm not sure that his recommendation is the best trade-off, nor that the situation is precisely comparable to pre-commit review. There definitely will be pre-commit review, there may or may not be any post-commit review. I'm willing to go with the "separate commit to reindent individual files" approach if there's a consensus that that makes for a cleaner git history. But I'm not 100% convinced it matters. regards, tom lane
В списке pgsql-hackers по дате отправления: