Hello,

Sorry about responding so late on this. Is the import into wicketstuff/wicketstuff done? because only the master branch and wicketstuff-p...@3267 are showing in github. There were 180 branches in the test import.

In the test import I had these questions: (which may be moot now that the real one is in the process of being deployed)

I was wondering about removing the git-svn-id: * lines from the commit messages. Are they of any use once we are a purely a git repository?

I guess we can go back later and add in git tags for the /tags branches.

What about branches like this (do you know what the @rev tags mean?):

  origin/wicketstuff-push
  origin/wicketstuff-p...@1941
  origin/wicketstuff-p...@1971
  origin/wicketstuff-p...@2597
  origin/wicketstuff-p...@3267

I did a git checkout -b wicketstuff-push origin/wicketstuff-push on the test repository and then gitk.

origin/wicketstuff-push seems to be the tip of the branch with the @rev versions pointing at historical points in the graph.

It looks like it should be safe to delete the @rev branches or maybe change them into git tags?

Mike

Go ahead. There's not much we can do otherwise?

Martijn

On Tue, Dec 28, 2010 at 5:13 PM, Martin Grigorov<mgrigo...@apache.org>  wrote:
I can confirm that my pre-github (git-svn) copy 'master' of wicketstuff-core
from sf.net is identical with the one from wicketstuff-test-import (pure
git).
Verified with 'diff -r -u' locally.

I *assume* the branches are OK too...

On Tue, Dec 28, 2010 at 4:59 PM, Igor Vaynberg<igor.vaynb...@gmail.com>wrote:

are we good to go with this import? if so i can push it into the
proper repo and we can move forward...

-igor

On Fri, Dec 24, 2010 at 6:23 AM, Igor Vaynberg<igor.vaynb...@gmail.com>
wrote:
alright, import is done here

https://github.com/wicketstuff/wicketstuff-test-import

its not perfect, but workable. if we decide its good enough we can put
it into the proper repo.

-igor

On Thu, Dec 23, 2010 at 11:19 PM, Igor Vaynberg<igor.vaynb...@gmail.com>
wrote:
my import is still running, at r5012 so almost there. im going to bed,
so i will check it out tomorrow morning.

cheers,
-igor


On Thu, Dec 23, 2010 at 11:17 PM, Michael O'Cleirigh
<michael.ocleir...@rivulet.ca>  wrote:
Igor,

Let me know if your current import works or not.

I've given up on the JGit approach.  At least right now there isn't
enough
time to get it to work properly for extracting branches.

There may be a way to extract branches using the git filter-branch
command
directly; it seemed to work in my test but gitk doesn't show the
branches as
I would expect it so I'm not sure.

Regards,

Mike


im importing using the u...@wicketstuff.org addresses, but i dont
think that matters much.

-igor

On Thu, Dec 23, 2010 at 5:45 PM, Michael O'Cleirigh
<michael.ocleir...@rivulet.ca>    wrote:
Hello,

In testing last week it took about 5 hours to clone from svn using
git-svn.
  I've been trying to trying to get a version of the repository ready
but
its
been taking longer than I wanted.

I think what we will need to do is to clone it locally and prepare it
and
then upload to github.

My java migration program can extract the first and last names of the
developers and create the git-authors.txt usable when importing.  I
changed
the email addresses to svn-usern...@users.sourceforge.net  since
this is
an
actual routable address.  (This is what Martin Funk used in his
wicketpit
migration from 2009).

In my testing I have:

1. checked out the entire project history into master (i.e. no
branches)
2. used JGit to rewrite the entire history using the git users and
removing
the svn-git-id lines.

This part works fine and the accented characters (umlauts) have been
inserted properly.  I could not get git-svn to write them in
properly.
The next part involves extracting branches from the master.   My code
works
for identifying the first commit to contain a path and to extract
from
the
original commits the branch sub-tree.  But I still need to delete the
non-branch files on the initial branch commit.

When the repository is large using windows is not recommended (I was
using
windows 7 on a quad core 3.4 Ghz Athlon and the git performance on my
Xen
vps was 50% faster).  It was taking me 45 minutes to checkout master.
  Yesterday I bought a faster hard disk and installed Linux and the
performance seems a lot faster.

I think I should be able to get it to work today (I'm on vacation now
so
my
productivity should be improved).

I'll update the list in a few hours if my git repository looks like
it
will
be viable.

Mike

import is running really slow, even from a local copy of svn repo.
going to take a while...

-igor

On Thu, Dec 23, 2010 at 10:54 AM, Igor Vaynberg<
igor.vaynb...@gmail.com>
  wrote:
running a manual import right now with git svn, lets see how that
goes.
-igor

On Thu, Dec 23, 2010 at 10:50 AM, Martijn Dashorst
<martijn.dasho...@gmail.com>      wrote:
"Import ran too long.  Try running locally with svn2git or
git-svn."
On Thu, Dec 23, 2010 at 8:57 AM, Igor
Vaynberg<igor.vaynb...@gmail.com>
  wrote:
gah. i will try a manual one and see if that goes better. can you
forward the error message to me, i didnt get one...

-igor

On Thu, Dec 23, 2010 at 9:29 AM, Martijn Dashorst
<martijn.dasho...@gmail.com>      wrote:
I received an error message that the import has failed.

Martijn

On Thu, Dec 23, 2010 at 6:24 AM, Jeremy Thomerson
<jer...@wickettraining.com>      wrote:
On Wed, Dec 22, 2010 at 3:35 PM, Igor
Vaynberg<igor.vaynb...@gmail.com>wrote:

i started the import here:

https://github.com/wicketstuff/wicketstuff

-igor

I removed everyone from the SF.net project except Igor,
Martijn,
and
myself.
  I took SVN commit permissions away from the three of us.  This
should
prevent anyone from accidentally committing to the repo now
that it
is
moved.

Once I hear from Igor that we are "good to go" at GH, I'll "svn
delete *" or
"svn mkdir ALL_CODE_IS_MOVED; svn mv * ALL_CODE_IS_MOVED/" and
"svn
add
README_FIRST_WE_HAVE_MOVED_TO_GITHUB.txt".

--
Jeremy Thomerson
http://wickettraining.com
*Need a CMS for Wicket?  Use Brix! http://brixcms.org*

--
Become a Wicket expert, learn from the best:
http://wicketinaction.com

--
Become a Wicket expert, learn from the best:
http://wicketinaction.com




Reply via email to