On 2/7/07, David Harvey <[EMAIL PROTECTED]> wrote:
>
> I am very annoyed with hg. We have been using it for several months
> now, but still, pretty much *every* time I use it, I get confused as to
> what I am doing. It always ends up wasting a lot of my time. The
> warnings/error messages are unhelpful, and somehow the whole system is
> very unintuitive to me. Yes, I tried the tutorial in the SAGE manual,
> and it didn't help.
>
> By way of contrast, I find svn dead easy. I'm not suggesting we use
> svn... it's probably not appropriate for SAGE, but I'm just making the
> point that there does exist a version control system that I find easy
> to use. I also recall finding darcs much easier to use than hg.

I think that I've been spoiled by darcs. I hate that you have to clone
your directory to patch things, because you can't choose what changes
to send, like in darcs. I think I miss that the most. Also, patches
are not text files by default, although you can "export" them.

Does anyone know how to unapply patches from a repository?

I also hate that when you commit changes without a message, hg exits
abnormally WITHOUT telling you that you need a message to commit your
changes.

didier

>
> I don't know if I'm the only one having this problem. If it's just me,
> then I guess I just have to get my act together and work it out. But if
> there are others on this list with the same problem, please speak up.
> If there are enough of us, then I would be *really* happy if someone
> could do a "Mercurial for Dummies" talk at SD3. Just go through a few
> typical workflows, and explain rwhat the hell is going on in each one.
>
> David
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to