Re: Deploying more robust hg-git replication for gecko

2013-09-06 Thread Aki Sasaki
On 9/5/13 10:32 AM, Nicolas B. Pierron wrote: On 09/05/2013 09:51 AM, Ehsan Akhgari wrote: On 2013-09-03 9:39 PM, Aki Sasaki wrote: On 9/3/13 8:25 AM, Ehsan Akhgari wrote: 2. How frequently are these branches updated? The current job is running on a 5 minute cron job. We can, of course,

Re: Deploying more robust hg-git replication for gecko

2013-09-05 Thread Ehsan Akhgari
On 2013-09-03 9:39 PM, Aki Sasaki wrote: On 9/3/13 8:25 AM, Ehsan Akhgari wrote: Thanks for the update on this, John! I have a number of questions about this: 1. On the issue of the hg tags, can you please be more specific about the problem that you're encountering? In my experience, git

Re: Deploying more robust hg-git replication for gecko

2013-09-03 Thread Ehsan Akhgari
Thanks for the update on this, John! I have a number of questions about this: 1. On the issue of the hg tags, can you please be more specific about the problem that you're encountering? In my experience, git deals with updated tags the same way as it does with any non-fast-forward merge, and

Re: Deploying more robust hg-git replication for gecko

2013-09-03 Thread Gregory Szorc
On 9/3/13 8:25 AM, Ehsan Akhgari wrote: 5. Is the git-mapfile generated from the conversion scrips available somewhere? (Mine is currently available here:

Re: Deploying more robust hg-git replication for gecko

2013-09-03 Thread Aki Sasaki
On 9/3/13 8:25 AM, Ehsan Akhgari wrote: Thanks for the update on this, John! I have a number of questions about this: 1. On the issue of the hg tags, can you please be more specific about the problem that you're encountering? In my experience, git deals with updated tags the same way as

Deploying more robust hg-git replication for gecko

2013-08-30 Thread John O'Duinn
(cross-posting to make sure this is not missed; please respond in dev-planning or bug#847727) tl,dr: we're moving replication of gecko+gaia repos to more robust systems. This email gives quick status, and summary of rollout plan. In the rush to B2G 1.0 release, we had to quickly stand up