Dear diary, on Fri, Aug 18, 2006 at 04:03:29PM CEST, I got a letter where Carl Worth <cworth@xxxxxxxxxx> said that... > * A single thingy I could publish for <URL> and <branch>. Ideally this > would have no whitespace in it and would be directly > cut-and-paste-able for use in either gitweb or the git command-line. Perhaps you could paste a fetch URL to some gitweb inputbox at the top of every page and it would show the right thing, sort of like mldonkey with ed2k URLs... > * A mechanism for not requiring me to invent tracking-branch names. I > end up manually doing a scheme with short prefixes for any given > repository. It would be nice if I could configure that (in > .git/remotes/<something> say) once so that any new branch I pulled > would get its properly named tracking branch. And git could find the > right remotes file by matching up the URL. We already have .git/refs/remote/ where the tracking branches are just the same name as on the other side, we only need to start really using it. -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ Snow falling on Perl. White noise covering line noise. Hides all the bugs too. -- J. Putnam - 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