On Fri, Oct 14 2011, John Dickinson wrote: > But it's metadata about the code (a particular review pattern with a > particular vcs). VCS info does not belong in the code. I'll admit that I > like a dotfile in the repo much better than I like rfc.sh in the repo, but > I'd prefer to keep info about remotes, review processes, and other repo > metadata out of the repo. If this is something for a particular VCS (as the > proposed git-review is), it should use the established locations for that > particular VCS. In this case, git-review should pull info from the .git > directory (more specifically, the git config data).
I understand your statement, but I don't think it is the good thing to fight for this. You can consider that .gitignore is VCS metadata too. But it exists everywhere. Every file is a file particular to a tool used in a project, being Python, a Makefile, or a Git file. :) -- Julien Danjou // eNovance http://enovance.com // ✉ julien.dan...@enovance.com ☎ +33 1 49 70 99 81 _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
