# Git repository refactoring and Status update **URL:** \ **Category:** Radiant CMS\ **Created:** [June 21, 2008, 3:37pm UTC](https://www.ruby-forum.com/t/git-repository-refactoring-and-status-update/141064 "2008-06-21T15:37:19Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\ **Post date:** [June 21, 2008, 3:37pm UTC](https://www.ruby-forum.com/t/git-repository-refactoring-and-status-update/141064/1 "2008-06-21T15:37:19Z")
The Radiant git repository has been refactored! All of the existing code has been added to a new, neutral, ‘radiant’ user on github. Please update your watches and remove your forks of [github.com/seancribbs/radiant](http://github.com/seancribbs/radiant) – it will be disappearing soon. I will do my best to incorporate existing pull requests into the new repositories. What does this mean for you? 1. The Radiant core application is separated from all of the ancillary projects, including extensions. 2. Extensions are in individual repos, making it easier to develop them in parallel. 3. You can watch or ignore whichever parts of the project interest you most. 4. We will have an extension registry and install/uninstall sooner rather than later! 5. Extensions will get more attention as we will be able to bring in more contributors who are interested most in specific extensions. 6. We will soon support rake radiant:freeze:edge pulling from the git repo. 7. We will be phasing out the old SVN repository, which happens to be several commits old anyway because git-svn broke on me. Cheers, Sean ---
**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\ **Post date:** [June 21, 2008, 6:48pm UTC](https://www.ruby-forum.com/t/git-repository-refactoring-and-status-update/141064/2 "2008-06-21T18:48:53Z")
Sean C. wrote: > What does this mean for you? > > 1. The Radiant core application is separated from all of the ancillary > projects, including extensions. > 2. Extensions are in individual repos, making it easier to develop them > in parallel. > 3. You can watch or ignore whichever parts of the project interest you > most. > 4. We will have an extension registry and install/uninstall sooner > rather than later! > 5. Extensions will get more attention as we will be able to bring in > more contributors who are interested most in specific extensions. > 6. We will soon support rake radiant:freeze:edge pulling from the git > repo. > 7. We will be phasing out the old SVN repository, which happens to be > several commits old anyway because git-svn broke on me. This is all great news. Rock on. ---
**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\ **Post date:** [June 23, 2008, 5:12pm UTC](https://www.ruby-forum.com/t/git-repository-refactoring-and-status-update/141064/3 "2008-06-23T17:12:48Z")
Sean C. wrote: > The Radiant git repository has been refactored! All of the existing > code has been added to a new, neutral, ‘radiant’ user on github. Please > update your watches and remove your forks of > [github.com/seancribbs/radiant](http://github.com/seancribbs/radiant) – it will be disappearing soon. I will > do my best to incorporate existing pull requests into the new > repositories. Great work, Sean! I’m looking forward to the extension registry. - Dave ---
**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\ **Post date:** [June 24, 2008, 1:12am UTC](https://www.ruby-forum.com/t/git-repository-refactoring-and-status-update/141064/4 "2008-06-24T01:12:27Z")
On Mon, Jun 23, 2008 at 5:12 PM, David P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Sean C. wrote: > > > The Radiant git repository has been refactored! All of the existing > > code has been added to a new, neutral, ‘radiant’ user on github. Please > > update your watches and remove your forks of > > [github.com/seancribbs/radiant](http://github.com/seancribbs/radiant) – it will be disappearing soon. I will > > do my best to incorporate existing pull requests into the new > > repositories. [GitHub - radiant/radiant: Radiant is a no-fluff, open source content management system designed for small teams.](http://github.com/radiant/radiant/tree/master) seems to have been imported “raw” (without the git history). It would be nice if the svn history was kept intact. I suppose the plan is to have all the Radiant subprojects in separate Git repos from now on. To my regret it seems like they have all been imported without git-svn. In my opinion, the initial import to [http://github.com/seancribbs/radiant/tree/master](http://github.com/seancribbs/radiant/tree/master) got it right. It seems to have been imported with git-svn. Is there any particular reason why git-svn has (apparently) not been used in the migration of the other radiant git repos? Cheers, Aslak ---
**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\ **Post date:** [June 24, 2008, 1:17am UTC](https://www.ruby-forum.com/t/git-repository-refactoring-and-status-update/141064/5 "2008-06-24T01:17:43Z")
On Tue, Jun 24, 2008 at 1:10 AM, aslak hellesoy [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > [GitHub - radiant/radiant: Radiant is a no-fluff, open source content management system designed for small teams.](http://github.com/radiant/radiant/tree/master) seems to have been > imported “raw” (without the git history). It would be nice if the svn > history was kept intact. One more recommendation: Git has a feature akin to svn:externals called Git submodule that lets you “symlink” other Git repos. Have you considered using this feature for the stuff under vendor and vendor/plugins? A lot of the stuff that is there is already at Github, and the stuff that isn’t should be quick to clone up to Github/Gitorious. I think that in the long run it’s better to use Git submodule than keeping hard forks of the various libraries. Cheers, Aslak ---
**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\ **Post date:** [June 24, 2008, 1:22am UTC](https://www.ruby-forum.com/t/git-repository-refactoring-and-status-update/141064/6 "2008-06-24T01:22:24Z")
Aslak, git-svn doesn’t play nicely when you have other remote git repositories, as I found multiple times when trying to keep the old SVN up-to-date. At the time I created the new repos, SVN was out of date, and so it was not prudent to import from that. I may go back and recreate the main radiant repository from the older git repo, gaining all of its inherited SVN and git history. However, doing that for some 23 repositories is not my idea of fun. Sean ---
**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\ **Post date:** [June 24, 2008, 1:18am UTC](https://www.ruby-forum.com/t/git-repository-refactoring-and-status-update/141064/7 "2008-06-24T01:18:19Z")
On Jun 23, 2008, at 4:10 PM, aslak hellesoy wrote: > > > repositories. > > > In my opinion, the initial import to > > > [http://github.com/seancribbs/radiant/tree/master](http://github.com/seancribbs/radiant/tree/master) got it right. It > > > seems to have been imported with git-svn. > > Is there any particular reason why git-svn has (apparently) not been > used in the migration of the other radiant git repos? > > Cheers, > Aslak My guess is because they no longer follow the same structure they used to. It wouldn’t make sense to have a history duplicated of a huge number of commits that don’t even apply to the sliver of code that not exists in its own repo. -Alex > **[Beautiful Pixel](https://beautifulpixel.com/)** > > A log of random code experiments and semi-useless thoughts from some software developer named Alex... ---
**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\ **Post date:** [June 24, 2008, 1:24am UTC](https://www.ruby-forum.com/t/git-repository-refactoring-and-status-update/141064/8 "2008-06-24T01:24:10Z")
aslak hellesoy wrote: > One more recommendation: Git has a feature akin to svn:externals > called Git submodule that lets you “symlink” other Git repos. Have you > considered using this feature for the stuff under vendor and > vendor/plugins? A lot of the stuff that is there is already at Github, > and the stuff that isn’t should be quick to clone up to > Github/Gitorious. I think that in the long run it’s better to use Git > submodule than keeping hard forks of the various libraries. I’ll give that some thought and toss it around with the other committers. However, it may suffer the same weaknesses as svn:externals, which is dependency on the availability of those other repositories, which I don’t like much. Sean ---
**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\ **Post date:** [June 24, 2008, 1:32am UTC](https://www.ruby-forum.com/t/git-repository-refactoring-and-status-update/141064/9 "2008-06-24T01:32:21Z")
On Tue, Jun 24, 2008 at 1:23 AM, Sean C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > I’ll give that some thought and toss it around with the other committers. > However, it may suffer the same weaknesses as svn:externals, which is > dependency on the availability of those other repositories, which I don’t > like much. True, but as long as everything is hosted at the same host (Github) - if one repo is available, so will the others. Aslak ---
**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\ **Post date:** [June 24, 2008, 1:31am UTC](https://www.ruby-forum.com/t/git-repository-refactoring-and-status-update/141064/10 "2008-06-24T01:31:11Z")
On Tue, Jun 24, 2008 at 1:21 AM, Sean C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Aslak, > > git-svn doesn’t play nicely when you have other remote git repositories, as > I found multiple times when trying to keep the old SVN up-to-date. At the > time I created the new repos, SVN was out of date, and so it was not prudent > to import from that. I may go back and recreate the main radiant repository > from the older git repo, gaining all of its inherited SVN and git history. > However, doing that for some 23 repositories is not my idea of fun. Understood. SCM history is overrated anyway 🙂 Aslak