phases and pulls, workaround for read-only pull?

[Pierre-Yves David]

On Fri, Dec 14, 2012 at 02:04:39PM +0100, Axel Hecht wrote:
> 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.

You can use a hook to mark outgoing changeset public.

You could also pull from main repo before amending but that wont solve all possible case.



-- 
Pierre-Yves David

http://www.logilab.fr/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20121218/de00adae/attachment.asc>