Excerpts from Alexander Staubo's message of Tue Oct 30 21:13:35 +0100 2007:
> On 10/30/07, Panu A Kalliokoski <[EMAIL PROTECTED]> wrote:
> > Currently, giving a new repository for darcs put, pull or push changes
> > the default repository for darcs pull and push commands. However,
> > usually I mostly want to deal with a primary repository ("upstream" /
> > "central") with pull and push, and only randomly make pull and push
> > operations from elsewhere.
> [snip]
> > Would it be possible to only set the default repository during an
> > initial get / put, and leave it at that indefinitely? This would have
> > been the correct way of operation in all of my situations thus far.
>
> You can accomplish this pretty much by adding these two lines to your
> ~/.darcs/defaults:
>
> pull no-set-default
> push no-set-default
>
> That said, I agree wholeheartedly that the current behaviour is the
> inverted and contrary to the way I, and every developer I know, use a
> version control system.
>
> We typically work with a single upstream, occasionally cherry-picking
> from other branches or shuttling patches off to special release
> branches, but generally "push" and "pull" *need* to remain consistent.
>
> This is not the only bad default in Darcs; --set-scripts-executable
> and --look-for-adds both enable behaviour that other version control
> systems consider dead obvious.
>
> These are also a points of confusion which I have noticed will trip up
> new users. Helping these people set up a sane config file works, and I
> do that a lot, but the default settings ought to be sane from the get
> go.
>
I would also prefer these default values to be inverted (backward
compatibility... still an issue). Hopefully ~/.darcs/defaults make this
easier.
--
Nicolas Pouillard aka Ertai
_______________________________________________
darcs-devel mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-devel
