Managing local changes I don't want to push?

Martin Sjögren martin.sjogren at jasper-da.com
Thu Aug 9 02:47:58 CDT 2007


Hello list, new mercurial user here.

I've recently started to use mercurial (long time user of cvs and
subversion, casual user of darcs) and I'm wondering if mercurial can
solve a problem of mine.

We use it in a more or less centralized style, having an "official
repository" that everybody pull from and push to, but people set up
other repositories too. Now, what I want to do is have some local
changes (e.g. an extra target in a Makefile) that I want to be applied
whenever the "official" Makefile changes, but I don't want these changes
to tag along when I push my changes back to the official repo.

I tried out MQ, but either I don't understand how to make it work for
me, or it can't do what I want to do... Am I right in that since
changesets depend linearly on each other, once I commit a changeset for
my local Makefile changes, all my further commits in that repository
will depend on it, so if I want to push another changeset, I can't do
that without including the Makefile change?

Is there another way to do it, or am I doomed to keep it as uncomitted
local changes the way I would in cvs/svn?


Thanks,
Martin



More information about the Mercurial mailing list