hi,
importing the pike-svn repo into git took 3 days. git-svn seems to have some issues there, as the process got slower and slower (and in the end git-svn had more than 300MB in ram (allocated 1GB))
the resulting repo had 178645 objects and a size of 1178MB. git-svn allocates another 1.5GB for statusinformation on each branch. (and because tags are branches, the 1729 tags result in as many branches)
however, after packing, the resulting repo ocupies a mere 44MB!!!
that alone is a good reason for me to use git, as it it gives me the whole repo in the same space as the checkout of a single revision in svn.
you can clone this repo from http://www.iaeste.at/~mbaehr/pike-svn.git the svn import info is removed from that repo.
when we switch to svn i'll try to make a repo available that contains the svn info to spare anyone else who wants ot use git-svn a 3day import.
greetings, martin.
On Mon, Oct 15, 2007 at 03:44:56PM +0200, Martin Bähr wrote:
you can clone this repo from http://www.iaeste.at/~mbaehr/pike-svn.git
copy the repo with wget if you want to see all the branches, since they are remote branches which are not reproduced using clone. (the objects are copied, but the branch info is not)
greetings, martin.
Martin B?hr wrote:
On Mon, Oct 15, 2007 at 03:44:56PM +0200, Martin B?hr wrote:
you can clone this repo from http://www.iaeste.at/~mbaehr/pike-svn.git
copy the repo with wget if you want to see all the branches, since they are remote branches which are not reproduced using clone. (the objects are copied, but the branch info is not)
I just fetched it from you. After using SVN/SVK for 2 years, I decided to drop SVN/SVK and use git for all my projects (after careful evaluation of the available alternatives). The following questions come to mind: - You imported from the Pike SVN repository; how up to date was/is that and do you now have all the information from SVN into git? - In order to track changes and/or push back changes I enter into my personal git, I should be tracking the CVS (bidirectionally), anyone tried that starting with the git you provided?
On Sat, Nov 17, 2007 at 08:07:40PM +0100, Stephen R. van den Berg wrote:
you can clone this repo from http://www.iaeste.at/~mbaehr/pike-svn.git
I just fetched it from you. After using SVN/SVK for 2 years, I decided to drop SVN/SVK and use git for all my projects (after careful evaluation of the available alternatives).
good choice :-)
The following questions come to mind:
- You imported from the Pike SVN repository; how up to date was/is that and do you now have all the information from SVN into git?
it is about a year old. however updating it using cvsimport was easy and did not take to long. when i get some time after the conference i'll publish the updated repo.
- In order to track changes and/or push back changes I enter into my personal git, I should be tracking the CVS (bidirectionally), anyone tried that starting with the git you provided?
i tried during the conference. updating from cvs went fine, using cvsexportcommit is a bit odd but also worked. (last commit from me is done that way)
however after that updating with cvsimport again seemed to cause some issues, but i am not sure what the reason is. i think cvsimport just recognizes that i already have the commit (since i made it) and does not update the branch.
i am definetly going to try to continue commiting to pike through git, so i'll work in figuring out what's the issue here. (it may just take a while since i am not really commiting that often :-)
greetings, martin.
Martin B?hr wrote:
On Sat, Nov 17, 2007 at 08:07:40PM +0100, Stephen R. van den Berg wrote:
The following questions come to mind:
- You imported from the Pike SVN repository; how up to date was/is that and do you now have all the information from SVN into git?
it is about a year old. however updating it using cvsimport was easy and did not take to long. when i get some time after the conference i'll publish the updated repo.
I'll have a go at it as well then, I just imported the Roxen tree through cvsimport, only took about 2 hours (over the net) and the resulting repo is 22MB roughly. You can't imagine how much of a relief it was to notice that importing didn't barf on the Swedish characters sometimes in the logs and/or files (this was an absolute nightmare when trying to convert to SVN/SVK).
- In order to track changes and/or push back changes I enter into my personal git, I should be tracking the CVS (bidirectionally), anyone tried that starting with the git you provided?
however after that updating with cvsimport again seemed to cause some issues, but i am not sure what the reason is. i think cvsimport just recognizes that i already have the commit (since i made it) and does not update the branch.
You checked it into the origin branch? Maybe you should not be checking it into origin, but push it upstream without doing that, then let cvsimport pull it again. I'll look into it as well.
On Sat, Nov 17, 2007 at 08:56:47PM +0100, Stephen R. van den Berg wrote:
You can't imagine how much of a relief it was to notice that importing didn't barf on the Swedish characters sometimes in the logs and/or files (this was an absolute nightmare when trying to convert to SVN/SVK).
yes, i remember marc talking about that and i tried to find out what the issue was as i had no problems importing to git.
however after that updating with cvsimport again seemed to cause some issues, but i am not sure what the reason is. i think cvsimport just recognizes that i already have the commit (since i made it) and does not update the branch.
You checked it into the origin branch?
no, i keep two branches, one for cvs import and one to work in. i made the exportcommit from the working branch and then tried the cvsimport on the import branch.
i tried clearing the cvsps cache, but that made no difference.
greetings, martin.
On Sun, Nov 18, 2007 at 12:58:53PM +0100, Martin Baehr wrote:
no, i keep two branches, one for cvs import and one to work in. i made the exportcommit from the working branch and then tried the cvsimport on the import branch.
i tried clearing the cvsps cache, but that made no difference.
i tried importing again just now, and this time it worked. no clue why it didn't work yesterday.. possible difference was that this time i had the cvs branch checked out while running import.
my commit and the equivvalent commit from cvsimport got a different sha because my branch was not uptodate. need to consider that. running cvsexportcommit is like push and should generally only be done on an uptodate repo to make sure the commit applies cleanly.
sothe workflow should be:
work in local branch, commit stuff; run cvsimport on cvs branch; rebase local branch onto cvs branch; cvsexportcommit rebased branch; cvsimport to update cvsbranch;
greetings, martin.
You can't imagine how much of a relief it was to notice that importing didn't barf on the Swedish characters sometimes in the logs and/or files (this was an absolute nightmare when trying to convert to SVN/SVK).
yes, i remember marc talking about that and i tried to find out what the issue was as i had no problems importing to git.
Weird, I had no such problems whatsoever when making my Subversion import. All you need to do is put --encoding=latin1 on the commandline of cvs2svn (this is needed because CVS does not store any information about what charset it is using for metadata, neither implicitly nor explicitly).
Martin B?hr wrote:
importing the pike-svn repo into git took 3 days. git-svn seems to have some issues there, as the process got slower and slower (and in the end git-svn had more than 300MB in ram (allocated 1GB))
Do you still have the magic incantations handy which you used for "git-svn init" ?
On Fri, Feb 22, 2008 at 09:50:30PM +0100, Stephen R. van den Berg wrote:
importing the pike-svn repo into git took 3 days. git-svn seems to have some issues there, as the process got slower and slower (and in the end git-svn had more than 300MB in ram (allocated 1GB))
Do you still have the magic incantations handy which you used for "git-svn init" ?
i just followed the instructions for git-svn, nothing magic there.
greetings, martin.
pike-devel@lists.lysator.liu.se
-
Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum -
Martin B?hr -
Martin Baehr
-
Martin Bähr
-
Stephen R. van den Berg