Clone hg tamarin-central for ActionMonkey work


Status Graveyard
Server Operations
11 years ago
3 years ago


(Reporter: Mardak, Assigned: reed)





11 years ago
Clone hg to with same access privs as

We'll use this for development before pushing changes to tamarin-central.

Comment 1

11 years ago
Need approval from brendan.


11 years ago
Assignee: server-ops → reed

Comment 2

11 years ago
Brendan gave verbal approval. Doing this now.

Comment 3

11 years ago
This has been set up.
Last Resolved: 11 years ago
Resolution: --- → FIXED
I said this to Reed in person, but for the record: I don't think it's a good use of either his or my time to be pointy-haired (sorry Reed) gatekeepers here. Hg, which I'm starting to dislike intensely, really makes you clone to do sandboxed development (perhaps named branches may help some day). So I expect a lot of cloning. As Woody Allen said in "Sleeper", "never clone alone". Can we make it easier and more distributed and less file-ticket-to-bug-IT-and-brendan to clone what needs to be cloned?


Comment 5

11 years ago
That would be a question for aravind/reed. I do think that anyone with Hg access should be able to clone any tree they want in their personal area ( And that small groups should be able to create feature repos at will, e.g.

Note that IT doesn't have to do a clone... they can just create an empty repo and the person using the branch can pull/push to it to get things started.
Group: mozillaorgconfidential
I'm not saying it matters to me either way, but the benefit of cloning on the server vs cloning locally and pushing to an empty repo is that the server clone will end up sharing the majority of the repo data on the server and thus save significantly on disk space over time. Other than that it's all the same AFAIK.
Product: → Graveyard
You need to log in before you can comment on or make changes to this bug.