From: Johannes Schindelin
Date: Tue, 16 Oct 2007 10:49:58 GMT
Subject: cogito and remote#branch, was Re: [PATCH] Git homepage: remove all the references to Cogito
Message-ID:
In-Reply-To: <20071016021933.GH12156@machine.or.cz>
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 http://repo.or.cz/.
> >
> >
> >
> > -- Cogito
> > --
> > -Cogito
> > -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.
> >
> > - StGIT
> > - Stacked Git 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