On Sun, Jan 28, 2007 at 01:22:46AM +0100, Matthias Lederhofer wrote: > --- > There are some other places where direct editing of .git/config is > suggested. I'd rather tell the user to use repo-config and add a note > that repo-config saves the configuration to .git/config (or > ~/.gitconfig with --global) which can be edited by hand too. > cat .git/config to show the remote configuration can be replaced by > git-repo-config -l | grep '^remote\.' > --- Based on the followup I think what makes sense is to continue with some mixture of the two approaches--mainly editing the configuration file directly, but providing frequent references to the git-repo-config/git-config manpage so people know where to find the details. I've added a few more references to the manpage, along with a few other updates, including an initial import of Linus's discussion of dangling objects, and brief dicussions of reflogs, fsck, and pruning: git://linux-nfs.org/~bfields/git.git master http://www.fieldses.org/~bfields/git-user-manual.html --b. - 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