On Wed, Sep 29, 2010 at 5:41 PM, Daniel Stutzbach
wrote:
> Obviously, it would not be possible to write hooks that reject changesets
Of course, this is one of the more interesting ways to use hooks.
Since there's no current expectation that running our own will be a
problem, why don't we convert
On Wed, Sep 29, 2010 at 4:25 PM, "Martin v. Löwis" wrote:
> Of course, with a hosted service, you often can't run hooks at all,
> so the effort to write them is also reduced :-)
>
It should be easy to write an automated script that pulls the latest changes
from the hosted service and then runs ho
> Do we expect Mercurial to require more, less, or about the same amount of
> babysitting as the current Subversion repository?
The ongoing effort is to manage write access; this is not going to
change with Mercurial.
With a hosted service, you still need someone who gives write
permissions to
On 2010-09-29, at 15:26 , Tarek Ziadé wrote:
> On Wed, Sep 29, 2010 at 2:36 PM, wrote:
>> On 01:13 am, st...@holdenweb.com wrote:
>>> I see that Atlassian have just taken over BitBucket, the Mercurial
>>> hosting company. IIRC Atlassian offered to host our issue tracking on
>>> JIRA, but in the e
On Wed, Sep 29, 2010 at 16:43, Barry Warsaw wrote:
> Do we expect Mercurial to require more, less, or about the same amount of
> babysitting as the current Subversion repository? I would think no more and
> Subversion hasn't been much of a problem.
Yeah, should be about the same.
Cheers,
Dirkj
On Sep 28, 2010, at 09:13 PM, Steve Holden wrote:
>I see that Atlassian have just taken over BitBucket, the Mercurial
>hosting company. IIRC Atlassian offered to host our issue tracking on
>JIRA, but in the end we decided to eat our own dog food and went with
>roundup.
I was an advocate for JIRA
On Wed, Sep 29, 2010 at 2:36 PM, wrote:
> On 01:13 am, st...@holdenweb.com wrote:
>>
>> I see that Atlassian have just taken over BitBucket, the Mercurial
>> hosting company. IIRC Atlassian offered to host our issue tracking on
>> JIRA, but in the end we decided to eat our own dog food and went w
On 9/29/2010 6:32 AM, Ben Finney wrote:
> Dirkjan Ochtman writes:
>
>> Still, I think the flexibility of self-hosting (in terms of hooks and
>> extension -- for example the one that would allow lookup by SVN rev)
>> should win out here.
>
> Not only the flexibility, but the autonomy. Hosting the
On 01:13 am, st...@holdenweb.com wrote:
I see that Atlassian have just taken over BitBucket, the Mercurial
hosting company. IIRC Atlassian offered to host our issue tracking on
JIRA, but in the end we decided to eat our own dog food and went with
roundup.
I'm wondering if they'd be similarly int
On 2010-09-29, at 11:50 , Antoine Pitrou wrote:
> On Wed, 29 Sep 2010 09:03:29 +0200
> Dirkjan Ochtman wrote:
>>
>> Anyway, I don't think using Bitbucket buys us much. It could be nice
>> to keep a mirror there for redundancy and because it might make
>> contributing slightly easier for non-commi
On Wed, Sep 29, 2010 at 11:35, Victor Stinner
wrote:
> Can't we rewrite the history when converting from svn to hg to use real names
> instead of logins?
I've been doing that since the start, look at the test repo on hg.p.o.
Cheers,
Dirkjan
___
Python
Am 29.09.2010 09:03, schrieb Dirkjan Ochtman:
> On Wed, Sep 29, 2010 at 03:13, Steve Holden wrote:
>> I see that Atlassian have just taken over BitBucket, the Mercurial
>> hosting company. IIRC Atlassian offered to host our issue tracking on
>> JIRA, but in the end we decided to eat our own dog fo
Dirkjan Ochtman writes:
> Still, I think the flexibility of self-hosting (in terms of hooks and
> extension -- for example the one that would allow lookup by SVN rev)
> should win out here.
Not only the flexibility, but the autonomy. Hosting the source code on
systems either paid for by PSF fund
On Wed, 29 Sep 2010 09:03:29 +0200
Dirkjan Ochtman wrote:
>
> Anyway, I don't think using Bitbucket buys us much. It could be nice
> to keep a mirror there for redundancy and because it might make
> contributing slightly easier for non-committers, but it won't allow
> doing all kinds of custom ho
Le mercredi 29 septembre 2010 08:58:49, Brett Cannon a écrit :
> The trick would be managing accounts. I would assume either everyone
> would need bitbucket accounts to add as contributors to a repo, or a
> dummy python-dev user account would be created where select core devs
> could add SSH keys t
On Wed, Sep 29, 2010 at 08:58, Brett Cannon wrote:
> Looking at their pricing model, we don't need permission; public repos
> can have unlimited contributors. Plus bitbucket supports CNAMEs so we
> would also be able to still have hg.python.org for accessing the
> repos.
>
> The trick would be man
On Wed, Sep 29, 2010 at 03:13, Steve Holden wrote:
> I see that Atlassian have just taken over BitBucket, the Mercurial
> hosting company. IIRC Atlassian offered to host our issue tracking on
> JIRA, but in the end we decided to eat our own dog food and went with
> roundup.
>
> I'm wondering if th
On Tue, Sep 28, 2010 at 18:13, Steve Holden wrote:
> I see that Atlassian have just taken over BitBucket, the Mercurial
> hosting company. IIRC Atlassian offered to host our issue tracking on
> JIRA, but in the end we decided to eat our own dog food and went with
> roundup.
That's right. Enough o
I see that Atlassian have just taken over BitBucket, the Mercurial
hosting company. IIRC Atlassian offered to host our issue tracking on
JIRA, but in the end we decided to eat our own dog food and went with
roundup.
I'm wondering if they'd be similarly interested in supporting our Hg
server. Or is
19 matches
Mail list logo
