Stephen Lau writes:
> Richard Lowe wrote:
>> Mike Kupfer writes:
>>
>>
"Rich" == Richard Lowe writes:
> But with Mercurial it could also be implemented as a tag in a single
> gate workspace.
>
>>> Rich> No, it couldn't, tags introduce cha
Mike Kupfer writes:
>> "Rich" == Richard Lowe writes:
>
>>> But with Mercurial it could also be implemented as a tag in a single
>>> gate workspace.
>
> Rich> No, it couldn't, tags introduce changesets.
>
> Okay, but why is that a problem? Instead of , we
> have plus one changeset to set t
Mike Kupfer writes:
>> "Ken" == Ken Erickson writes:
>
> Ken> I'm not sure throwing away the collective wisdom of 20 years worth
> Ken> of gatekeepers is such a good idea.
>
> I agree, but I think we should try to separate out the "wisdom" parts
> from the artifacts of the implementation.
W
Richard Lowe wrote:
> Mike Kupfer writes:
>
>
>>> "Rich" == Richard Lowe writes:
>>>
But with Mercurial it could also be implemented as a tag in a single
gate workspace.
>> Rich> No, it couldn't, tags introduce changesets.
>>
>> Okay, but why is t
> "Rich" == Richard Lowe writes:
>> But with Mercurial it could also be implemented as a tag in a single
>> gate workspace.
Rich> No, it couldn't, tags introduce changesets.
Okay, but why is that a problem? Instead of , we
have plus one changeset to set the tag. What am I
missing?
mike
> "Ken" == Ken Erickson writes:
Ken> I'm not sure throwing away the collective wisdom of 20 years worth
Ken> of gatekeepers is such a good idea.
I agree, but I think we should try to separate out the "wisdom" parts
from the artifacts of the implementation.
For example, I (and others) want t
>> Anyway, how will commit notifications be handled using hg? Has there
>> been a policy decision about this? Will a hook be used to email
>> the changes to a list? If so, then buglist really doesn't have
>> to change much.
>
>Yes, they'd continue going to onnv-notify, at least in part.
>buglis
Rich tried posting to the temporary list that Ken had set up, which
didn't work, so he asked me to forward this. I think after this
message we can all go back to using scm-migration-dev.
mike
--- Forwarded Message
Subject: Re: thoughts about 'buglist' script
From:Richard Lowe
To:
