Hi, On Tue, 16 Oct 2007, Petr Baudis wrote: > On Mon, Oct 15, 2007 at 11:38:00PM +0200, Paolo Ciarrocchi wrote: > > @@ -286,15 +285,6 @@ a gitweb interface, at <a href="http://repo.or.cz/";>http://repo.or.cz/</a>.</p> > > > > <dl> > > > > -<dt id="cogito">Cogito</dt> > > -<dd> > > -<a href="http://git.or.cz/cogito/";>Cogito</a> > > -is a popular version control system on top of Git. > > -It aims at seamless user interface and ease of use, providing > > -generally smoother user experience than the "raw" Git interface > > -and indeed also many other version control systems. However, it > > -also lacks many advanced capabilities of Git and is currently > > -being slowly phased out.</dd> > > > > <dt id="stgit">StGIT</dt> > > <dd><a href="http://www.procode.org/stgit/";>Stacked Git</a> provides > > I'm not sure this is good idea, Cogito is still quite frequently used > and it should be documented that it exists. I agree. But maybe it could be marked as unmaintained? Maybe someone steps up to maintain it. Or, even better, comes up with a list of "this is what I like do regularly with cogito, but there's no easy way with core git" issues. In related news, I recently thought about the url#branch issue. There were three arguments against it AFAIR: "#" is a comment marker, and this syntax is not extensible to more than one branch names. And that the branch name is not really a part of the URL. Turns out that I am not so sure about the last two issues. It is easily extensible to more than one branch by remote#branch1#branch2, and in a very real sense, this is a resource locator. And we could replace the "#" by every character that is illegal in ref names as well as URLs. I propose SPC. ('#' is allowed in refnames.) Ciao, Dscho - 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
