Am Samstag, 7. März 2009 04:27:48 schrieb bugs buggy: > On 3/2/09, Per Inge Mathisen <[email protected]> wrote: > > On Mon, Mar 2, 2009 at 8:18 AM, Gerard Krol <[email protected]> wrote: > I did svn clone whatever-repo and after it pulled it all down, without > doing anything to the files, I did: git diff, and it showed a ton of > stuff. No clue what that means, but for me it worked quite well on Windows. But then I did not do a git-svn-clone.
> I then checked with the GUI versions (tortoisegit and Qgit) and it > also showed the same. They will unlikely show something different, because they just parse git's output. > Booted up the linux box, and tried the same url and did git diff, and > it worked as it should. > (btw, trying to do a svn clone from GNA is very, very, VERY slow. You are downloading each and every of the nearly 7k svn revision. It is kinda supposed to be slow. > Don't know what the issue is, but I aborted it when it had 'not > responding' on the shell title.) > > So where does this leave us? Well, since GNA is being very pesky, I > don't really have a choice. > > What I was thinking is, that we could start a new repo here: > http://github.com/plans (the free open-source plan has a limit of > 300MB, but, they will allow more if we e-mail them and ask), then as a > bonus, it can import the GNA svn repo in when we create the project. There are other services, like gitorious and whatnot, as well. Maybe give them at least a look before we decide for one. > Then try more git goodness with ssh access and commits with them. If you like I can give you (temporary) ssh access to my server, so you can play there a little. > The other things I was wondering was, what will happen to CIA if we > move the repo? If github does not support CIA, we would setup the notification script on some other server, which syncs with github. > How does git deal with line endings? (cr+lf vs lf) I just set > core.autocrlf = true, and that is it? Doesn't the sha change because > of the difference? I don't really know, but in the past it seemed to work ok. I recommend using an editor which supports Unix line endings though, since somehow we had lots of line ending changes in that repos' commits. But maybe the guys did not know about the autocrlf option. And my assumption is that that conversion gets only applied to the working copy, and is converted to Unix line endings when you commit. (And back to "native" when you checkout, just as SVN does.) > How would trac be affected by this? There is a plugin for Trac which allows using Git as a backend. It is not extremely stunning, but it works. --DevUrandom
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
