On 5/10/06, Linus Torvalds <torvalds@xxxxxxxx> wrote:
You _can_ be user-friendly and machine-parseable at the same time!
Good one. I'm following this thread with interest, but it feels we've been attacked by the 'bike shed bug' in the act of redesigning Windows.ini. As an end-user, I have personally stayed away from the increasingly complex scheme for remotes waiting for it to settle, and stuck with the old-styled .git/branches stuff which is slam-dunk simple and it just works. The normal non-branch config options don't need any of this fancy stuff. And I think the branches is reasonably well managed as files as is done in .git/remotes which is trivial to work on with standard shell commands. What I mean is that I can grep them trivially to ask "how many remotes pull from server X" or from repo Y. Or via rsync. Also -- repo config is tricky in the sense of scope. I want all my "dev" repos of different projects on my laptop to have mostly the same config but radically different remotes listings. So... call me old-styled... but I'm happy with one-file-per-remote. Was it broken to start with? Should we restart the track renames flameway instead? cheers, martin - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html