Bug 46132 - freedesktop account for gerrit.documentfoundation.org
Summary: freedesktop account for gerrit.documentfoundation.org
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: contrib (show other bugs)
Version: 3.4.4 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-15 13:05 UTC by Björn Michaelsen
Modified: 2013-10-16 08:59 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Björn Michaelsen 2012-02-15 13:05:40 UTC 

    


    


      



        
          Comment 1
        

        
          Björn Michaelsen

        

        
        

        
          2012-02-15 13:10:16 UTC
        

      






Robert Einsle <r.einsle@documentfoundation.org> wrote:
wrt the git-repo, I only checked out anonymously for now. Who can setup an ssh key for gerrit?

Can we have an fdo-account for gerrit?

    


    


      



        
          Comment 2
        

        
          Michael Meeks

        

        
        

        
          2012-02-16 08:08:07 UTC
        

      






A quick two line explanation of why gerrit is cool, and why it needs to push would be cool, and we'll get some more eyes on this. Might be nice to attach the ssh key you want to use as well :-)

    


    


      



        
          Comment 3
        

        
          Thomas Arnhold

        

        
        

        
          2013-10-16 02:15:18 UTC
        

      






Is this still an issue?

    


    


      



        
          Comment 4
        

        
          Björn Michaelsen

        

        
        

        
          2013-10-16 08:59:18 UTC
        

      






closing as WORKSFORME as gerrit is clearly syncing to freedesktop.

    



  






  














    


  Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.