Git-mirror of Drupal core now on Github
For anyone who's been using/playing with my Git-mirror of Drupal core CVS at http://git.lion47.com/ (which is currently on a slow and unstable connection), I have created a mirror on Github, so feel free to use that instead. I will keep updating it every 12 hours. http://github.com/mikl/drupal/tree/master -- Kind regards, Mikkel Høgh <mikkel@hoegh.org>
On Saturday 11 October 2008 05:20:24 am Mikkel Høgh wrote:
For anyone who's been using/playing with my Git-mirror of Drupal core CVS at http://git.lion47.com/ (which is currently on a slow and unstable connection), I have created a mirror on Github, so feel free to use that instead. I will keep updating it every 12 hours.
http://github.com/mikl/drupal/tree/master -- Kind regards,
Mikkel Høgh <mikkel@hoegh.org>
The public clone url for that repo is: git://github.com/mikl/drupal.git As the one given above fails. Thanks for this, Mikkel!
Thank you - i've been waiting for this. Dmitri On Oct 11, 2008, at 3:20 AM, Mikkel Høgh wrote:
For anyone who's been using/playing with my Git-mirror of Drupal core CVS at http://git.lion47.com/ (which is currently on a slow and unstable connection), I have created a mirror on Github, so feel free to use that instead. I will keep updating it every 12 hours.
http://github.com/mikl/drupal/tree/master -- Kind regards,
Mikkel Høgh <mikkel@hoegh.org>
It would be ideal for core development if it could update very frequently like once per hour. That way we would be less likely to generate fuzzy patches. Most cron runs will result in no git push but perhaps you have reasons why thats not desireable. On Sat, Oct 11, 2008 at 6:20 AM, Mikkel Høgh <mikkel@hoegh.org> wrote:
For anyone who's been using/playing with my Git-mirror of Drupal core CVS at http://git.lion47.com/ (which is currently on a slow and unstable connection), I have created a mirror on Github, so feel free to use that instead. I will keep updating it every 12 hours.
http://github.com/mikl/drupal/tree/master -- Kind regards,
Mikkel Høgh <mikkel@hoegh.org>
No, no specific reason, besides not wanting to upset the admins at cvs.drupal.org – I do not know how much strain a git-cvsimport puts on the CVS server, but when I first set this up, I wanted to be on the safe side. If it's okay to do so, I have no problems increasing the frequency. That server is doing almost nothing anyways :) And yes, as Sam said, the URL i posted earlier is to the Github HTML interface. The clone URL is git://github.com/mikl/drupal.git – sorry for the confusion. -- Kind regards, Mikkel Høgh <mikkel@hoegh.org> On 11/10/2008, at 17.03, Moshe Weitzman wrote:
It would be ideal for core development if it could update very frequently like once per hour. That way we would be less likely to generate fuzzy patches. Most cron runs will result in no git push but perhaps you have reasons why thats not desireable.
On Sat, Oct 11, 2008 at 6:20 AM, Mikkel Høgh <mikkel@hoegh.org> wrote:
For anyone who's been using/playing with my Git-mirror of Drupal core CVS at http://git.lion47.com/ (which is currently on a slow and unstable connection), I have created a mirror on Github, so feel free to use that instead. I will keep updating it every 12 hours.
http://github.com/mikl/drupal/tree/master -- Kind regards,
Mikkel Høgh <mikkel@hoegh.org>
I'm assuming that your workflow looks something like this: $ cd /path/to/local/git-cvsimport/of/drupal/core $ git cvsimport -a $ git push --mirror <remote ref name for your github repo> Which will pull in all the recent changes from core, then push them out to your github repo. If that's the case, git-cvsimport doesn't put much strain on the servers, as it does its work by incrementally importing changesets. If you were very concerned about server load, you could always run the git-cvsimport off a copy of drupal cvs that you keep rsync'd locally, but I suspect that the performance impact on drupal's cvs server would be negligible in either case. Of course, if we were talking contrib, that might be a little different... :) s On Saturday 11 October 2008 10:32:31 am Mikkel Høgh wrote:
No, no specific reason, besides not wanting to upset the admins at cvs.drupal.org – I do not know how much strain a git-cvsimport puts on the CVS server, but when I first set this up, I wanted to be on the safe side.
If it's okay to do so, I have no problems increasing the frequency. That server is doing almost nothing anyways :)
And yes, as Sam said, the URL i posted earlier is to the Github HTML interface. The clone URL is git://github.com/mikl/drupal.git – sorry for the confusion. -- Kind regards,
Mikkel Høgh <mikkel@hoegh.org>
On 11/10/2008, at 17.03, Moshe Weitzman wrote:
It would be ideal for core development if it could update very frequently like once per hour. That way we would be less likely to generate fuzzy patches. Most cron runs will result in no git push but perhaps you have reasons why thats not desireable.
On Sat, Oct 11, 2008 at 6:20 AM, Mikkel Høgh <mikkel@hoegh.org> wrote:
For anyone who's been using/playing with my Git-mirror of Drupal core CVS at http://git.lion47.com/ (which is currently on a slow and unstable connection), I have created a mirror on Github, so feel free to use that instead. I will keep updating it every 12 hours.
http://github.com/mikl/drupal/tree/master -- Kind regards,
Mikkel Høgh <mikkel@hoegh.org>
Yeah, that's basically my cron-script sans a bit of the nitty-gritty details, but it is an incremental operation, although the average runtime is around 13 seconds when there are no changes. I've upped the frequency, so it now runs at :07 every hour :) -- Kind regards, Mikkel Høgh <mikkel@hoegh.org> On 11/10/2008, at 18.50, Sam Boyer wrote:
I'm assuming that your workflow looks something like this:
$ cd /path/to/local/git-cvsimport/of/drupal/core $ git cvsimport -a $ git push --mirror <remote ref name for your github repo>
Which will pull in all the recent changes from core, then push them out to your github repo. If that's the case, git-cvsimport doesn't put much strain on the servers, as it does its work by incrementally importing changesets. If you were very concerned about server load, you could always run the git-cvsimport off a copy of drupal cvs that you keep rsync'd locally, but I suspect that the performance impact on drupal's cvs server would be negligible in either case.
Of course, if we were talking contrib, that might be a little different... :)
s
On Saturday 11 October 2008 10:32:31 am Mikkel Høgh wrote:
No, no specific reason, besides not wanting to upset the admins at cvs.drupal.org – I do not know how much strain a git-cvsimport puts on the CVS server, but when I first set this up, I wanted to be on the safe side.
If it's okay to do so, I have no problems increasing the frequency. That server is doing almost nothing anyways :)
And yes, as Sam said, the URL i posted earlier is to the Github HTML interface. The clone URL is git://github.com/mikl/drupal.git – sorry for the confusion. -- Kind regards,
Mikkel Høgh <mikkel@hoegh.org>
On 11/10/2008, at 17.03, Moshe Weitzman wrote:
It would be ideal for core development if it could update very frequently like once per hour. That way we would be less likely to generate fuzzy patches. Most cron runs will result in no git push but perhaps you have reasons why thats not desireable.
On Sat, Oct 11, 2008 at 6:20 AM, Mikkel Høgh <mikkel@hoegh.org> wrote:
For anyone who's been using/playing with my Git-mirror of Drupal core CVS at http://git.lion47.com/ (which is currently on a slow and unstable connection), I have created a mirror on Github, so feel free to use that instead. I will keep updating it every 12 hours.
http://github.com/mikl/drupal/tree/master -- Kind regards,
Mikkel Høgh <mikkel@hoegh.org>
participants (4)
-
Dmitri Gaskin -
Mikkel Høgh -
Moshe Weitzman -
Sam Boyer