phases and pulls, workaround for read-only pull?

Axel Hecht l10n.moz at gmail.com
Fri Dec 14 13:04:39 UTC 2012


Hi,
I'd like to modify changesets locally unless their pulled to a different
repo. Phases looks promising, but the pull doesn't change the phase of the
pulled changesets to public, due to being read-only.

Does someone have a way to work around that, or achieve the same thing in a
different way?

Background:

At mozilla, we have a few webtools which I'd like to export to hg
changesets. At the same time, I don't want them to go through security
review at the level of scrutiny we'd require for write access to our hg
repos.
For most of them, a "check-in" step is rather alien. Think pootle, for
example. I'd love for them to have the author attribution right, too. The
idea was to have a local bot that checks for modifications in the database,
and exports to source code, and commits. If the modifications are from the
same author, and possibly the last commit being recent, it'd commit
--amend. But only if nobody else pulled that changeset yet to uplift it
into our code repos.

Makes sense?

Thanks

Axel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20121214/abea0479/attachment-0002.html>


More information about the Mercurial mailing list