On Mon, Oct 01, 2007 at 11:44:38PM +0200, Luca Capello wrote: > Hi David! > > On Mon, 01 Oct 2007 21:06:57 +0200, David Roundy wrote: > > On Mon, Oct 01, 2007 at 07:26:59PM +0200, Luca Capello wrote: > >> It could be useful to have an official file _darcs/description > >> which is a small phrase to describe the repository, created by > >> `darcs init` and retrieved when `darcs get`. This can be used > >> later by darcsweb as well as by darcs-server. > > > > Perhaps you're looking for the feature _darcs/prefs/motd? This is > > manually created, and is used to print a little message when > > pulling/getting. > > Well, this is not exactly what I was searching for. What if someone > want to set both _darcs/prefs/motd and _darcs/prefs/description? > Moreover, from what I could see, _darcs/prefs/motd is not propagated > when `darcs get`.
It's intentional that motd isn't propogated on darcs get, because that creates a new repository, which has a new identity (e.g. the new repository won't be "the central darcs repository, unstable branch"). If description is intended to describe the contents of the repository, why not put it in the repository itself? Do you want to propogate it on darcs get, but not on darcs pull? > My idea is more general: _darcs/prefs/description could be also used > to identify the repository you're in. Since I thought that this > information belongs to each repository, I decided to go for this > wishlist bug. > > > Maybe this bug should be rerouted to darcsweb, to make darcsweb use > > the motd for its description? > > For the reasons above, I don't think darcsweb should use it. I'm not sure what your reasoning is. It still seems to me like the perfect fit for darcsweb to describe a repository. -- David Roundy Department of Physics Oregon State University -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
