On Sunday, July 03, 2011 06:46:15 PM Tom Lane wrote: > A look at the git-notes man page says that you can only have one note > per commit, but you can edit that note, and git does track the revision > history of each note. > > I think that we should adopt "git notes" as a better solution than > making dummy whitespace changes when we want to put a commit-message > correction into the commit history (you listening, Bruce?). There is git commit --allow-empty btw
> But as Robert says, this still leaves the committers as the gatekeepers > for the information, so it's not clear to me that this is a good way to > solve the problems that Greg was talking about originally. I'd rather > have a solution that offloads the work from the committers. I don't think its that hard to write a hook which allows notes changes for a different set of people than source changes. Whether the people wanting to annotate commits are ok with using git I do not know. Andres -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
