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 – 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?
- The Radiant core application is separated from all of the ancillary
projects, including extensions.
- Extensions are in individual repos, making it easier to develop them
in parallel.
- You can watch or ignore whichever parts of the project interest you
most.
- We will have an extension registry and install/uninstall sooner
rather than later!
- Extensions will get more attention as we will be able to bring in
more contributors who are interested most in specific extensions.
- We will soon support rake radiant:freeze:edge pulling from the git
repo.
- 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
Sean C. wrote:
What does this mean for you?
- The Radiant core application is separated from all of the ancillary
projects, including extensions.
- Extensions are in individual repos, making it easier to develop them
in parallel.
- You can watch or ignore whichever parts of the project interest you
most.
- We will have an extension registry and install/uninstall sooner
rather than later!
- Extensions will get more attention as we will be able to bring in
more contributors who are interested most in specific extensions.
- We will soon support rake radiant:freeze:edge pulling from the git
repo.
- 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.
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 – 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.
On Mon, Jun 23, 2008 at 5:12 PM, David P. [email protected]
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 – 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. 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 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
On Tue, Jun 24, 2008 at 1:10 AM, aslak hellesoy
[email protected] wrote:
GitHub - radiant/radiant: Radiant is a no-fluff, open source content management system designed for small teams. 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
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
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 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
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
On Tue, Jun 24, 2008 at 1:23 AM, Sean C. [email protected]
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
On Tue, Jun 24, 2008 at 1:21 AM, Sean C. [email protected]
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