The page that you get when you click on a patch would be better if it included the author and date, in addition to the comment and cetera.

And dependency graph!  And timeline!

Regards,

Zooko

My thought about this bug is that we should get rid of darcs.cgi and  
adopt one of the other projects like darcsweb or darcs+trac as the  
"official" darcs cgi. (I'm not suggesting we merge the projects)

Any thought?

Thanks,
Jason

On Jan 25, 2006, at 2:05 PM, Zooko wrote:

>
> New submission from Zooko <zooko@zooko.com>:
>
> The page that you get when you click on a patch would be better if  
> it included the author and date, in addition to the comment and  
> cetera.
>
> And dependency graph!  And timeline!
>
> Regards,
>
> Zooko
>
> ----------
> messages: 417
> nosy: droundy, tommy, zooko
> status: unread
> title: I wish darcs.cgi would tell me who, when on the patch  
> description page.
>
> ____________________________________
> Darcs issue tracker <bugs@darcs.net>
> <http://bugs.darcs.net/issue109>
> ____________________________________
>
> _______________________________________________
> darcs-devel mailing list
> darcs-devel@darcs.net
> http://www.abridgegame.org/cgi-bin/mailman/listinfo/darcs-devel

> My thought about this bug is that we should get rid of darcs.cgi and
> adopt one of the other projects like darcsweb or darcs+trac as the
> "official" darcs cgi. (I'm not suggesting we merge the projects)
>
> Any thought?

I much prefer darcsweb.  Are there any advantages of darcs.cgi over
the other choices?  And if there are any, are they things that
couldn't easily be implemented in the other choices?

On Thu, Jan 26, 2006 at 03:44:57AM +0000, Jason Dagit wrote:
> My thought about this bug is that we should get rid of darcs.cgi and  
> adopt one of the other projects like darcsweb or darcs+trac as the  
> "official" darcs cgi. (I'm not suggesting we merge the projects)
> 
> Any thought?

I've definitely considered that possibility--bascially splitting darcs.cgi
off into a separate project.  It's part of darcs because its predecessor
(darcs_cgi) was part of darcs, since it was compiled with darcs source
code.  darcs.cgi is pretty stable (meaning not under rapid development) at
the moment, and might actually develop more rapidly if it could easily be
branched without carrying along the rest of the darcs repository.

I'd like to hear from Will before splitting it, though... I'd be happy to
continue to host darcs.cgi on the darcs.net/abridgegame.org server.

The one advantage of having darcs.cgi included with darcs itself is that we
can simultaneously change darcs' interface and darcs.cgi's use of darcs.
But we really shouldn't link them *that* closely, since we'd like to keep
the interface stable for the benefit of darcsweb and others.
-- 
David Roundy
http://www.darcs.net

On Thu, 26 Jan 2006 14:09:20 +0000, "David Roundy" <bugs@darcs.net>
said:
> 
> David Roundy <droundy@darcs.net> added the comment:
> 
> On Thu, Jan 26, 2006 at 03:44:57AM +0000, Jason Dagit wrote:
> > My thought about this bug is that we should get rid of darcs.cgi and  
> > adopt one of the other projects like darcsweb or darcs+trac as the  
> > "official" darcs cgi. (I'm not suggesting we merge the projects)
> > 
> > Any thought?

I haven't tried installing darcsweb yet but it looks very nice.  I
wish the functionality followed darcs' terminology rather than git's
though... stuff like 'headblob' and 'commitdiff' is so foreign.

> I've definitely considered that possibility--bascially splitting
> darcs.cgi off into a separate project.  It's part of darcs because its
> predecessor (darcs_cgi) was part of darcs, since it was compiled with
> darcs source code.  darcs.cgi is pretty stable (meaning not under
> rapid development) at the moment, and might actually develop more
> rapidly if it could easily be branched without carrying along the rest
> of the darcs repository.
>
> I'd like to hear from Will before splitting it, though... I'd be happy to
> continue to host darcs.cgi on the darcs.net/abridgegame.org server.

To be honest I don't have much interest in major changes to darcs.cgi
and would be happy to let another project take its place.  The original
goal was to eliminate the maintenance burden of darcs_cgi and I think
that has been accomplished =)

That said, I would be happy to continue maintaining darcs.cgi in a
separate repository if some people prefer it and darcsweb cannot
accommodate their needs.

Regards,
Will

> I haven't tried installing darcsweb yet but it looks very nice.  I
> wish the functionality followed darcs' terminology rather than git's
> though... stuff like 'headblob' and 'commitdiff' is so foreign.

I poked at darcsweb for about 10 seconds one time.  It was ugly, and had all
this terminology that I didn't understand.  So I posted to the darcs-users
mailing list asking why anyone would use darcsweb over darcs.cgi.  No-one
replied.

So I'm still using darcs.cgi at the moment.

Regards,

Zooko

On Thu, Jan 26, 2006 at 10:40:32AM -0700, Will wrote:
> To be honest I don't have much interest in major changes to darcs.cgi and
> would be happy to let another project take its place.  The original goal
> was to eliminate the maintenance burden of darcs_cgi and I think that has
> been accomplished =)
> 
> That said, I would be happy to continue maintaining darcs.cgi in a
> separate repository if some people prefer it and darcsweb cannot
> accommodate their needs.

I would like darcs.cgi to stay around.  I'm not sure that darcsweb has
caught up with darcs.cgi in terms of functionality (e.g. information on the
file annotate page).  Plus, as Zooko says, some people prefer it.

So if someone wants to submit a patch removing darcs.cgi, then as soon as
we've got time to set up a separate darcs.cgi repository we can apply that
patch and simply direct users to both darcsweb and darcs.cgi in the manual.
-- 
David Roundy
http://www.darcs.net

For what it is worth, I am again using darcs.cgi,

http://allmydata.org/darcs.cgi

and once again wishing that it would show me who, when on the patch description
page.

:-)

I still don't like the look of darcsweb.

Regards,

Zooko

Zooko,

I assume this is an example of the "patch description page" you are referring to:

http://allmydata.org/darcs.cgi/tahoe/Makefile?c=annotate&p=20080201010040-e01fd-fa10b513b4c4bc0f4aeda81a3f29fc9b1405f3f2.gz&ch=20061130214005-4233b-866b0d7712fa01639fad15595fbd545b48876c52.gz&o=./Makefile

I could see about making that modification to the Perl or XSLT. I'll take the
ticket for now.

On Feb 8, 2008, at 10:16 AM, Mark Stosberg wrote:

> I assume this is an example of the "patch description page" you are  
> referring to:
>
> http://allmydata.org/darcs.cgi/tahoe/Makefile? 
> c=annotate&p=20080201010040-e01fd- 
> fa10b513b4c4bc0f4aeda81a3f29fc9b1405f3f2.gz&ch=20061130214005-4233b-86 
> 6b0d7712fa01639fad15595fbd545b48876c52.gz&o=./Makefile

Yes, exactly.

> I could see about making that modification to the Perl or XSLT.  
> I'll take the
> ticket for now.

Cool!

Regards,

Zooko

Zooko, I just sent a patch to darcs-devel for this.

I'm sorry it took 2 years for someone to get to it. Although, I found no joy in
working with XSLT myself. 

   Mark