[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] Re: [BUG] feature plan -- merge request headers

From: Colin Walters
Subject: Re: [Gnu-arch-users] Re: [BUG] feature plan -- merge request headers
Date: Thu, 27 May 2004 09:41:16 -0400

On Wed, 2004-05-26 at 23:43, Miles Bader wrote:
> Tom Lord <address@hidden> writes:
> > Or something like that, anyway --- it is a bit awkward that so many
> > other commands want to default to using the archive of the project
> > tree in `pwd` but fork is one that shouldn't.  Or should it?
> Many tla commands seem to default to the my-default-archive, when that's
> different than the current dir's archive.  Eg. `missing', `update', ...
> Probably most relevant:  tag defaults to my-default-archive, and tag's
> morally pretty close to fork...

Yeah.  I personally think we should make a big push towards using the
current tree archive.  my-default-archive works until you have two (or
more) personal archives.  I've unset it, since it's just not useful to

Using the current tree archive could be confusing for people who have
say all of ~ in arch - like when they do a 'tla get foo--bar--0'.  But
generally I think it makes sense for the less-common operations like 
get' to essentially always be fully-qualified, compared to operations
like 'replay' and 'star-merge'.

Attachment: signature.asc
Description: This is a digitally signed message part

reply via email to

[Prev in Thread] Current Thread [Next in Thread]