Okay, But then, information in the change logs is also mirrored in the repo log. For instance, could you not do “git log | grep <whatever>” ?
There have been great pains in the past to keep the tree “pure” on the basis that old stuff you might need can be pulled from the repo - is this not just an extension of that? It strikes me that keeping the logs in this manner is either a limitation in the repo tools, or just a workflow habit that can be changed. As you allude to, it’s your workflow that requires these files. In that case, could not your workflow simply access the repo history in “some-other-manner” ? If we are not going to keep functional but currently unused code visible, why bother with ancient-history ? Just seems a bit inconsistent. ( TBH, I actually don’t care that much, expect when in my own workflow i search for something - and keep forgetting to tell my command line to ignore ChangeLog* ;-) ) Steve "Harry" Coul [email protected] On May 7, 2014, at 8:05 PM, Darin Adler <[email protected]> wrote: > > On May 7, 2014, at 3:51 PM, Steven Coul (scoul) <[email protected]> wrote: > >> Or just remove them? > > I grep them all the time. I don’t think removing them would be a good thing. > > Many projects use the configuration management system’s own change logging > system rather than an explicit text file, but that’s not how we’ve been doing > things in WebKit. > > — Darin _______________________________________________ webkit-dev mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-dev
