Linus Torvalds <torvalds@xxxxxxxx> wrote: > So having a config option would solve the problem, but what annoys me > right now about the config options is that we really should have a > graphical front-end to setting those things or something, because while > _I_ don't have any issues with editing a ".git/config" file, I think we're > getting to the point where a lot of our problems are really about "you can > do it, but you have to know a lot about git to even know you can do it". Funny; I recently thought about rewriting Documentation/config.txt into a format that was not only easily read by asciidoc but which also had enough annotation data to render a Tk based UI from. That way we could always have the configuration option editor match the current set of configuration options, and also offer good help for them. E.g. use a checkbox for booleans, a tk_optionMenu for choice lists, and offer up the asciidoc text as "help" on the option. Its sort of in the back of my mind as something I'd like to do in git-gui, but right now branch management (creating, deleting, merging) is more important. Right now git-gui does have a GUI editor for its own configuration data that it keeps in "gui" sections of .git/config and ~/.gitconfig, and lets the user view and edit both. -- Shawn. - To unsubscribe from this list: 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