<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
14/02/2011 23:13, Max Rydahl Andersen wrote:
<blockquote
cite="mid:D98F459C-48C8-42F9-A5ED-93AB39A46DE5@redhat.com"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">My main contras for Git:
• It is poorly integrated with Windows and Eclipse.
</pre>
</blockquote>
<pre wrap="">
For Windows - is that really still the case ?
Last I tried it seemed to work fine ?
I used this <a class="moz-txt-link-freetext" href="http://help.github.com/win-git-installation/">http://help.github.com/win-git-installation/</a>
You had any specific bad experiences ?
About Eclipse, egit seem to be doing well ?
note, since git is darn fast I rarely eclipse tooling worth bothering with it...but again
I'll need to try on some more real examples to tell (hence my attempt on getting a real git repo to work with)
</pre>
</blockquote>
<br>
Egit doesn't support some specific functions. I looked through
<a class="moz-txt-link-freetext" href="http://wiki.eclipse.org/EGit/User_Guide">http://wiki.eclipse.org/EGit/User_Guide</a> and what I've found:<br>
<br>
<ul>
<li>Ad-hoc selection of the upstream branch to pull from</li>
<li>Deletion of tags is currently not supported in EGit</li>
<li>Signed tags</li>
<li>EGit 0.9 does not yet support authentication via HTTP or HTTPS
protocol. </li>
</ul>
I don't think they are significan't.<br>
<br>
<blockquote
cite="mid:D98F459C-48C8-42F9-A5ED-93AB39A46DE5@redhat.com"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap=""> • Git repo will be too big. Thus this is a question for me will be commits faster or not. It will big because:
• JBoss Tools SVN consists of pretty coupled projects, so we have(?) to create a single Git repo for all of them.
</pre>
</blockquote>
<pre wrap="">
well, its always been the intent these should get decoupled more and more with proper API's...one of the reasons that haven't happen
could be "blamed" on the fact the source is kept so close so its easy to "cheat" instead of defining proper API's.
</pre>
<blockquote type="cite">
<pre wrap=""> • There are a lot of binaries (jars, images, videos, giant zip-files, ...). If we want to have all SVN history in Git, we have to add all these binaries to the mirror. I expect it will take approx 5GB (SVN repo itself takes 7GB now).
</pre>
</blockquote>
<pre wrap="">
hmm - what repo are you using ? My repo with most projects built is a total of 3.7GB ...thus its (hopefully) much less since most are not versioned data.
We haven't had videos in the main repo for years and they were seldom changed thus shouldn't be too much - but we'll see.
btw. jars is often something that can be fixed - again, being sloppy about adding many big jars for testing a basic feature often is not needed.
</pre>
<blockquote type="cite">
<pre wrap="">Anyway, Max, if you succeed with creation of the mirror, please share it. I would like to play with it too :) I tried to create a Git mirror some time ago, but after a lot of attempts I decided that it is not possible on Windows without direct access to the SVN repo.
</pre>
</blockquote>
<pre wrap="">
yup - i've created a local svn mirror and it is currenty running svn2git to get a full repo to see how bad/big the damage is.
The final version i'll probably just include all the later branches/tags instead of the full story.
/max
_______________________________________________
jbosstools-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a>
</pre>
</blockquote>
</body>
</html>