Hi @Wido
Tried subscribing to commits mailing list, but got reply that I am already a 
subscriber.

Here is the reply received
Hi! This is the ezmlm program. I'm managing the
comm...@cloudstack.apache.org mailing list.

Acknowledgment: The address

   sateesh.chodapune...@accelerite.com

was already on the commits mailing list when I received
your request, and remains a subscriber.

Regards,
Sateesh

On 22/04/17, 4:53 AM, "Wido den Hollander" <w...@widodh.nl> wrote:

    I can't tell where this comes from.
    
    I suggest subscribing to comm...@cloudstack.apache.org to get the updates.
    
    Wido
    
    > Op 19 april 2017 om 15:46 schreef Boris Stoyanov 
<boris.stoya...@shapeblue.com>:
    > 
    > 
    > Yup, same here, no GitHub mails recently.. 
    > 
    > 
    > boris.stoya...@shapeblue.com 
    > www.shapeblue.com
    > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
    > @shapeblue
    >   
    >  
    > 
    > > On Apr 19, 2017, at 4:16 AM, Nicolas Vazquez <nicovazque...@gmail.com> 
wrote:
    > > 
    > > I noticed the same
    > > 
    > > 2017-04-18 12:15 GMT-03:00 Syed Ahmed <sah...@cloudops.com>:
    > > 
    > >> Same thing with me. I don't see any github activity on the ML since 
Friday.
    > >> 
    > >> On Tue, Apr 18, 2017 at 5:00 AM, Wido den Hollander <w...@widodh.nl>
    > >> wrote:
    > >> 
    > >>> 
    > >>>> Op 17 april 2017 om 19:58 schreef Sergey Levitskiy <
    > >>> sergey.levits...@autodesk.com>:
    > >>>> 
    > >>>> 
    > >>>> I used to receive emails from @dev on every change in git. The last
    > >>> email came on Friday. Is it expected?
    > >>> 
    > >>> I think so? I don't know how that worked previously. There is a
    > >>> com...@cloudstack.apache.org list though, you mind want to subscribe
    > >>> there.
    > >>> 
    > >>> Wido
    > >>> 
    > >>>> Example header:
    > >>>> 
    > >>>> From: serg38 <g...@git.apache.org>
    > >>>> To: <dev@cloudstack.apache.org>
    > >>>> References: <git-pr-2044-cloudst...@git.apache.org>
    > >>>> In-Reply-To: <git-pr-2044-cloudst...@git.apache.org>
    > >>>> Subject: [GitHub] cloudstack issue #2044: CLOUDSTACK-9877 Cleanup
    > >>> unlinked templates
    > >>>> 
    > >>>> Content-type: text/plain;
    > >>>>      charset="UTF-8"
    > >>>> Content-transfer-encoding: 7bit
    > >>>> 
    > >>>> Github user serg38 commented on the issue:
    > >>>> 
    > >>>>    https://github.com/apache/cloudstack/pull/2044
    > >>>> 
    > >>>> 
    > >>>> 
    > >>>> On 4/16/17, 10:02 PM, "Rohit Yadav" <rohit.ya...@shapeblue.com> 
wrote:
    > >>>> 
    > >>>>    Thanks Wido!
    > >>>> 
    > >>>>    ________________________________
    > >>>>    From: Wido den Hollander <w...@widodh.nl>
    > >>>>    Sent: 15 April 2017 15:59:33
    > >>>>    To: dev@cloudstack.apache.org
    > >>>>    Subject: [Github/Gitbox] Setting up your committer account
    > >>>> 
    > >>>>    Hi,
    > >>>> 
    > >>>>    Since yesterday we are using the Gitbox [0] services from ASF to
    > >>> have Github our 'primary' source of code.
    > >>>> 
    > >>>>    This means that we can now label PRs, merge them, close them, all
    > >> on
    > >>> Github.
    > >>>> 
    > >>>>    If you are a committer you have to be added to the 'cloudstack
    > >>> committers' team on Github and this is done automatically [1] once 
every
    > >> X
    > >>> hours.
    > >>>> 
    > >>>>    You however need to make sure that your Apache Profile/ID [2] has
    > >>> the right information and that you have 2FA [3] enabled on your Github
    > >>> account.
    > >>>> 
    > >>>>    The steps you need to take:
    > >>>> 
    > >>>>    - Make sure you are a CloudStack committer
    > >>>>    - Make sure you have a Github account
    > >>>>    - Enable 2FA [3] on your Github account
    > >>>>    - Update your Apache profile [2] and add your Github username
    > >>>> 
    > >>>>    Now, after a few hours the sync between ASF and Github should be
    > >>> completed and you are added to the right team on Github.
    > >>>> 
    > >>>>    If that doesn't work you might need to visit the Gitbox setup page
    > >>> [4] to link your Apache account to Github.
    > >>>> 
    > >>>>    Since we moved to Gitbox the URL of our Git repositories also
    > >>> changed, for example:
    > >>>> 
    > >>>>    - https://gitbox.apache.org/repos/asf/cloudstack.git
    > >>>> 
    > >>>>    If you want RO you can also sync from Github:
    > >>>> 
    > >>>>    - https://github.com/apache/cloudstack.git
    > >>>> 
    > >>>> 
    > >>>>    Once you are in the right group on Github you should be able to
    > >>> label PRs, close them, merge them and move.
    > >>>> 
    > >>>>    I have already created [5] a bunch of labels. If we all try to
    > >> label
    > >>> the PRs it will be much easier for people to filter PRs and review 
them.
    > >>>> 
    > >>>>    Questions? Ask!
    > >>>> 
    > >>>>    Wido
    > >>>> 
    > >>>>    [0]: https://gitbox.apache.org/
    > >>>>    [1]: https://issues.apache.org/jira/browse/INFRA-13885
    > >>>>    [2]: https://id.apache.org/
    > >>>>    [3]: https://help.github.com/articles/about-two-factor-
    > >>> authentication/
    > >>>>    [4]: https://gitbox.apache.org/setup/
    > >>>>    [5]: https://github.com/apache/cloudstack/labels
    > >>>> 
    > >>>>    rohit.ya...@shapeblue.com
    > >>>>    www.shapeblue.com
    > >>>>    53 Chandos Place, Covent Garden, London  WC2N 4HSUK
    > >>>>    @shapeblue
    > >>>> 
    > >>>> 
    > >>>> 
    > >>>> 
    > >>>> 
    > >>> 
    > >> 
    >
    




DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the 
property of Accelerite, a Persistent Systems business. It is intended only for 
the use of the individual or entity to which it is addressed. If you are not 
the intended recipient, you are not authorized to read, retain, copy, print, 
distribute or use this message. If you have received this communication in 
error, please notify the sender and delete all copies of this message. 
Accelerite, a Persistent Systems business does not accept any liability for 
virus infected mails.

Reply via email to