To be more clear: Rietveld + gcl (the way Chromium does reviews/checkins) has you specify a group of files which is called a change list. Part of each change list is a description. Reviewers use and critique this description, which is much like what's done with the ChangeLog.
Nothing lists out the modified functions like in your ChangeLog, but I guess that's just not something people commonly need. (And this could still be done by an automated script or a new search tool if that'd still be helpful to people.) If you haven't taken a look at http://codereview.chromium.org I strongly suggest you do so. Rietveld + gcl really do make life easier for us on Chromium--especially if you're a reviewer. (It would also solve the 3 lines of context issue that Julie brought up the other day.) J On Fri, Jul 3, 2009 at 10:59 AM, Peter Kasting <pkast...@google.com> wrote: > On Fri, Jul 3, 2009 at 10:55 AM, Darin Adler <da...@apple.com> wrote: > >> It's backwards to say that the ChangeLog is a workaround for lack of >> tools. Some day we may see a tool that works so well that we’d be willing to >> forgo change logs, but we need to see that tool in action first to see that >> it functions so well it obviates the need for ChangeLog. >> > > I once again suggest Rietveld, which has been suggested here before. > > PK > > _______________________________________________ > webkit-dev mailing list > webkit-dev@lists.webkit.org > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev > >
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
