partial commits

[Edward Peschko]

>> Hg attic will work for me, but I would think that hg would want that
>> functionality in the core, and probably integrated into hg update..
>
> I think the last time anyone suggested attic for the core, there was
> some concern about possible confusion with MQ -- in implementation
> terms, they overlap slightly.  (Personally, I think the main use cases
> are sufficiently different that it's not a huge concern.)

Talking about attic, I installed it, but I'm getting issues with
actually using it.

It seems to ignore my configuration file. According to instructions
on the mercurial wiki under AtticExtension, I should be able to put
the following in my hg file:

[extensions]
hgattic=/home/edp/hg_env/support/hgattic/attic.py

and be able to use 'hg attic', 'hg shelve' 'hg unshelve' and so on.
This issue is with 1.3.1, so I doubt it's a versioning thing.

Anyone use attic successfully? If so what setup steps were
required?

> Once you bow to the inevitable, drink the kool-aid, and accept that
> "yes, master, the changeset rules all" (chanted in a cult-like
> monotone), everything makes sense and you will put up with any amount
> of nonsense.

Ok, fine - changesets are the master, changesets are the alpha and the
omega, etc. etc. etc.

Great - there is such a thing as set logic, as well, ie:

IF my set of files has any overlap with change sets 1,2,3 on the server,
abort with error.

IF my set of files has *no* overlap, then process successfully.

> Which incompatibility issues in particular?  Mercurial moves fairly
> fast, and that's a pretty old version.  You really should try your
> workflow with 1.3.1 first.  Like, before posting.

Well, it's hard to check my workflow when everybody else at my
company is at .94. Even if I get attic working (see above) I'll
probably just use it for the patch functionality and default back
to 94 for committing, etc.

Anyways thanks, and any help on attic (from someone who has
set it up successfully) would be appreciated.

Ed