[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: migrating KDE's main modules to git
From:       Jeff Mitchell <mitchell () kde ! org>
Date:       2010-08-24 18:10:57
Message-ID: 4C740B31.3020906 () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On 8/24/2010 12:05 PM, Aaron J. Seigo wrote:
>> The people behind the sysadmin team will bring out the advise somewhere in
>> the next 2 weeks. We'll do our best to do it asap.
> 
> 2 weeks would be terrific.
> 
> once this document has arrived, if the scm list could provide a similar time 
> commitment for their decision making that would be most helpful to the rest of 
> us who are planning things that depend on the outcome.

At work I've been doing a parallel conversion from Gitorious to
Gitolite, and in the course of doing so have spent several hours writing
documentation on how to use Gitolite's commands and features (setting
permissions, setting repository descriptions, cloning and destroying
clones, the meanings of the outputs of the "info" and "expand" commands,
etc.).

With some slight modifications I will be able to turn this into a guide
for KDE Git users. This will be easier if I can put it somewhere on
projects.kde.org as the wiki markup syntax will be identical, but
regardless, the content is basically there. So in addition to the
document mentioned above, we'll be able to get this up in relatively
short order as well.

Once that's up (and especially once git.kde.org moves to its final
place, which has much more bandwidth), it may be worth creating a
sandbox that people can use to test out these commands and become
familiar with them.

--Jeff


["signature.asc" (application/pgp-signature)]

_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team


[prev in list] [next in list] [prev in thread] [next in thread]