| Message |
 |
Date: 2008-07-12 20:57
Sender: Tom Copeland
I think manual processing of requests is working out pretty well,
so, closing this...
Yours
Tom |
Date: 2008-04-27 13:20
Sender: Tom Copeland
Either way you want to go is fine with me. I'm easy, much like
Sunday morning.
I do agree that RubyForge's Git support is not as good as it
could be. It's still very much the centralized model - one git
repo per project. Perhaps we can figure out some way so that
a user can establish as many git repos as he wants to...
Yours,
Tom |
Date: 2008-04-27 11:11
Sender: 7rans
Dr. Nic, I suspect using branches would be too messy.
I would like to convert all my projects to Git (I've been wanting
to do that for a long time), but I have a lot of small projects.
I recently created a master project to hold most of these. How
ironic then, that I now need to register each and every project
instead in order to use Rubyforge's SCM with Git.
I guess it's okay, 30+ Rubyforge projects?
OTOH, I wonder if I should use GitHub and just use RubyForge
for distribution of these many small projects? How does RubyForge.org
feel about that?
|
Date: 2008-04-24 16:43
Sender: Dr Nic Williams
@7rans - I guess you can emulate multiple repos using
branches - one branch per package. |
Date: 2008-04-24 15:15
Sender: 7rans
I wish project's could have multiple git repos --one for each
package. Some projects have multiple packages and git does not
do subprojects, like SVN can. |
Date: 2008-04-16 22:16
Sender: Dr Nic Williams
This ticket can probably be closed now.
Answer: manual support tickets. |
Date: 2008-04-08 20:32
Sender: Dr Nic Williams
even if the initial back end implementation is just to send
Tom an email :) |
Date: 2008-04-08 20:31
Sender: Dr Nic Williams
Perhaps a big "I've git cloned my repo, and I'm ready to
kill my SVN repo and have a blank Git repo created for me!"
button would be a starting point for a UI? |
Date: 2008-04-08 20:26
Sender: Matt Todd
Will do.
But in general, I'm sure several folks would like to be able
to do this and may be beneficial to have a way for users to migrate
to Git without having to put ticket requests in.
Matt Todd |
Date: 2008-04-08 20:10
Sender: Tom Copeland
Hi Matt -
Sounds good, I'd be happy to erase the svn repo and create a
blank git repo - but could you file a separate support request
for that just so's I don't accidentally erase the wrong one or
whatever? Thanks!
Yours,
Tom |
Date: 2008-04-08 19:17
Sender: Matt Todd
+1
I'd definitely like to migrate to Git as well... even just a
way to wipe out the history of the SVN repo and create a Git
repo instead. I can just push all of that history from my GitHub
repo to the RubyForge one maintaining all of my history.
As far as git-svn is concerned, if you wanted to provide that,
go right ahead, but I'd prefer just being able to erase the old
SVN repo and create a new Git repo for me to push everything
to. I, and many like me, have already done the Git conversion
elsewhere and won't need to do the git-svn gymnastics again.
Matt Todd |
Date: 2008-04-07 22:58
Sender: Dr Nic Williams
If behind the scenes both the SVN + Git repos could exist,
then that might provide an option for developers to manually
migrate, and perhaps keep their SVN repos around as necessary.
I know the UI of rubyforge.org's SCM page doesn't lend
itself to supporting two SCMs; and I don't know if the
backend can support it. But theoretically it could be
possible as I assume they are two different systems +
support scripts.
Its probably the admin interface that is the hardest.
Can the CVS + SVN admin interfaces add a button "Create a
git repository too"?
Can a dual SCM project show both sets of admin interfaces?
Can the dual SCM admin interface have a "Shutdown CVS/SVN
repo forever?" button + supporting "Yes + Yes"
dual-checkbox
page?
Its more work, and no one likes more work, but its probably
nicer to let projects migrate themselves + their
user/developer base.
Of course, I can say all this because I'm not the one who'll
write the rubyforge php code :) |
Date: 2008-04-07 22:44
Sender: Tom Copeland
Hi Dr. Nic -
Thanks for the excellent post! Yes, we can definitely do
a conversion. What do you think is a good way to do this - just
convert the project to git and leave the svn repo in place and
let folks do the conversion themselves? Or use that git-svn
converter thingy and do it automatically?
Yours,
Tom |
Date: 2008-04-07 22:33
Sender: Dr Nic Williams
Discussion about rubyforge's new git support:
http://drnicwilliams.com/2008/04/08/git-for-rubyforge-accounts/ |
