You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Coty Sutherland <cs...@apache.org> on 2019/03/01 19:00:13 UTC
Re: Git migration read for testing
The email notifications work for when we push commits to the repository,
but it looks like we're missing emails when PRs are opened.
On Wed, Feb 27, 2019 at 9:03 AM Rémy Maucherat <re...@apache.org> wrote:
> On Wed, Feb 27, 2019 at 11:09 AM Mark Thomas <ma...@apache.org> wrote:
>
> > On 27/02/2019 09:44, Rémy Maucherat wrote:
> > > On Tue, Feb 26, 2019 at 1:33 PM Mark Thomas <ma...@apache.org> wrote:
> > >
> > >> All,
> > >>
> > >> https://github.com/apache/tomcat
> > >
> > >
> > > Trying my test commit, I can't push to the github repo. I probably
> missed
> > > something obvious.
> >
> > You need to make sure you have three green ticks here:
> > https://gitbox.apache.org/setup/
> >
> > If you haven't linked your ASF and GitHub accounts or setup MFA then it
> > can take an hour or so after you make those changes for write access to
> > be enabled (various systems need to sync in the background).
> >
>
> I had forgotten about this as the Tomcat repo commit info was already
> linked to my account. Thanks for the help !
>
> Rémy
>
>
> >
> > Mark
> >
> >
> > >
> > > Rémy
> > >
> > >
> > >>
> > >>
> > >> is now ready for testing.
> > >>
> > >> It should contain:
> > >> branches
> > >> - master (9.0.x)
> > >> - 8.5.x
> > >> - 7.0.x
> > >>
> > >> Tags:
> > >> - one for each 7.0.x, 8.5.x and 9.0.x release
> > >>
> > >> Tags have all been renamed to follow a a.b.c-MODIFIERn format for
> > >> version number where modifier is RC or M.
> > >>
> > >> The repository is probably read/write for all committers now but
> please
> > >> refrain from making any changes until we confirm that all is well.
> > >>
> > >> If you have some time available now, please test this new repository
> and
> > >> report and questions or concerns to this thread.
> > >>
> > >> Assuming no issues are discovered, I'd like to formally move over to
> git
> > >> later today.
> > >>
> > >> Mark
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> > >> For additional commands, e-mail: dev-help@tomcat.apache.org
> > >>
> > >>
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: dev-help@tomcat.apache.org
> >
> >
>
Re: Git migration read for testing
Posted by Michael Osipov <mi...@apache.org>.
Am 2019-03-01 um 21:50 schrieb Mark Thomas:
> On 01/03/2019 19:54, Mark Thomas wrote:
>> On 01/03/2019 19:00, Coty Sutherland wrote:
>>> The email notifications work for when we push commits to the repository,
>>> but it looks like we're missing emails when PRs are opened.
>>
>> ACK. I'll talk to infra.
>
> Fixed.
>
> FYI we have the option to route commits to one location and PRs +
> comments to another. At the moment, everything goes to dev@
>
> Some projects have separate commits@ and notifications@ lists (and
> possibly issues@ as well).
>
> Personally, I like it all in one place and tend to filter everything
> into a single folder anyway. But I wanted to mention that the option was
> there.
I'd opt for commits to commits@ and PRs to dev@. For those who'd like
see commits will need to subscribe to it. Commits on dev@ produce a lot
of traffic not necessarily related to dev discusssions.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Git migration read for testing
Posted by Mark Thomas <ma...@apache.org>.
On 01/03/2019 20:58, Rémy Maucherat wrote:
> On Fri, Mar 1, 2019 at 9:50 PM Mark Thomas <ma...@apache.org> wrote:
>
>> On 01/03/2019 19:54, Mark Thomas wrote:
>>> On 01/03/2019 19:00, Coty Sutherland wrote:
>>>> The email notifications work for when we push commits to the repository,
>>>> but it looks like we're missing emails when PRs are opened.
>>>
>>> ACK. I'll talk to infra.
>>
>> Fixed.
>>
>
> Looks like it :)
>
>>
>> FYI we have the option to route commits to one location and PRs +
>> comments to another. At the moment, everything goes to dev@
>>
>> Some projects have separate commits@ and notifications@ lists (and
>> possibly issues@ as well).
>>
>> Personally, I like it all in one place and tend to filter everything
>> into a single folder anyway. But I wanted to mention that the option was
>> there.
>>
>
> It is true other projects may have more mailing lists, but I'm not
> convinced right now.
>
> BTW, I made a commit on github one hour ago, but it still isn't on gitbox.
> Isn't this bad ?
Infra have been dealing with some abusive traffic to Gitbox. It got
behind. I think I can manually sync it. Let me look. Yes, I can. Done.
Hmm. I might need to manually trigger the commit mails...
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Git migration read for testing
Posted by Rémy Maucherat <re...@apache.org>.
On Fri, Mar 1, 2019 at 9:50 PM Mark Thomas <ma...@apache.org> wrote:
> On 01/03/2019 19:54, Mark Thomas wrote:
> > On 01/03/2019 19:00, Coty Sutherland wrote:
> >> The email notifications work for when we push commits to the repository,
> >> but it looks like we're missing emails when PRs are opened.
> >
> > ACK. I'll talk to infra.
>
> Fixed.
>
Looks like it :)
>
> FYI we have the option to route commits to one location and PRs +
> comments to another. At the moment, everything goes to dev@
>
> Some projects have separate commits@ and notifications@ lists (and
> possibly issues@ as well).
>
> Personally, I like it all in one place and tend to filter everything
> into a single folder anyway. But I wanted to mention that the option was
> there.
>
It is true other projects may have more mailing lists, but I'm not
convinced right now.
BTW, I made a commit on github one hour ago, but it still isn't on gitbox.
Isn't this bad ?
Rémy
Re: Git migration read for testing
Posted by Mark Thomas <ma...@apache.org>.
On 01/03/2019 19:54, Mark Thomas wrote:
> On 01/03/2019 19:00, Coty Sutherland wrote:
>> The email notifications work for when we push commits to the repository,
>> but it looks like we're missing emails when PRs are opened.
>
> ACK. I'll talk to infra.
Fixed.
FYI we have the option to route commits to one location and PRs +
comments to another. At the moment, everything goes to dev@
Some projects have separate commits@ and notifications@ lists (and
possibly issues@ as well).
Personally, I like it all in one place and tend to filter everything
into a single folder anyway. But I wanted to mention that the option was
there.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: Git migration read for testing
Posted by Mark Thomas <ma...@apache.org>.
On 01/03/2019 19:00, Coty Sutherland wrote:
> The email notifications work for when we push commits to the repository,
> but it looks like we're missing emails when PRs are opened.
ACK. I'll talk to infra.
Mark
>
> On Wed, Feb 27, 2019 at 9:03 AM Rémy Maucherat <re...@apache.org> wrote:
>
>> On Wed, Feb 27, 2019 at 11:09 AM Mark Thomas <ma...@apache.org> wrote:
>>
>>> On 27/02/2019 09:44, Rémy Maucherat wrote:
>>>> On Tue, Feb 26, 2019 at 1:33 PM Mark Thomas <ma...@apache.org> wrote:
>>>>
>>>>> All,
>>>>>
>>>>> https://github.com/apache/tomcat
>>>>
>>>>
>>>> Trying my test commit, I can't push to the github repo. I probably
>> missed
>>>> something obvious.
>>>
>>> You need to make sure you have three green ticks here:
>>> https://gitbox.apache.org/setup/
>>>
>>> If you haven't linked your ASF and GitHub accounts or setup MFA then it
>>> can take an hour or so after you make those changes for write access to
>>> be enabled (various systems need to sync in the background).
>>>
>>
>> I had forgotten about this as the Tomcat repo commit info was already
>> linked to my account. Thanks for the help !
>>
>> Rémy
>>
>>
>>>
>>> Mark
>>>
>>>
>>>>
>>>> Rémy
>>>>
>>>>
>>>>>
>>>>>
>>>>> is now ready for testing.
>>>>>
>>>>> It should contain:
>>>>> branches
>>>>> - master (9.0.x)
>>>>> - 8.5.x
>>>>> - 7.0.x
>>>>>
>>>>> Tags:
>>>>> - one for each 7.0.x, 8.5.x and 9.0.x release
>>>>>
>>>>> Tags have all been renamed to follow a a.b.c-MODIFIERn format for
>>>>> version number where modifier is RC or M.
>>>>>
>>>>> The repository is probably read/write for all committers now but
>> please
>>>>> refrain from making any changes until we confirm that all is well.
>>>>>
>>>>> If you have some time available now, please test this new repository
>> and
>>>>> report and questions or concerns to this thread.
>>>>>
>>>>> Assuming no issues are discovered, I'd like to formally move over to
>> git
>>>>> later today.
>>>>>
>>>>> Mark
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
>>>>> For additional commands, e-mail: dev-help@tomcat.apache.org
>>>>>
>>>>>
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: dev-help@tomcat.apache.org
>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org