[prev in list] [next in list] [prev in thread] [next in thread] 

List:       darcs-users
Subject:    Re: [darcs-users] Re: Onto which other patches does a patch depend?
From:       Thomas Zander <TZander () factotummedia ! nl>
Date:       2005-01-08 11:23:32
Message-ID: 20050108112332.GB18625 () factotummedia ! nl
[Download RAW message or body]


On Fri, Jan 07, 2005 at 08:41:37PM -0500, Michael Conrad wrote:
> > I like darcs rollback alot and think that without it, it will be
> > harder in darcs than in cvs to "undo" something.
>
> A while back someone suggested the idea of hiding patches.  (reverting the
> changes in a patch, while still keeping the patch "somewhere" to optionally
> reapply at a later time.)
> 
> This has an equivalent effect to what David suggested with get --to-patch
> foo, but seems more user friendly to me, and keeps the user from having to
> manage a new branch.  (by manage, I mean giving it a name, remembering what
> unwanted patches it contains, seeing it in directory listings, etc)

Going through darcs to get that list seems like more work to me, making it
less to the user and due to the lower complexity the user will understand it
better.
Darcs chose directories as branches over CVS's hiding of branches for a reason,
this looks like a step back.

IMO the user should just choose the name of his branch properly.
I have a 'waitForNewXYZLib' branch, for example.

-- 
Thomas Zander

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]