Started by Dwachs, October 25, 2013, 01:31:09 PM
0 Members and 1 Guest are viewing this topic.
Quote from: Max-Max on October 25, 2013, 03:25:40 PMWell, I did installed and tried to fork the experimental and had somewhat success. I found a TortoiseGIT but the nomeclature is quite different from SVN so I didn't understood really how to do the things I'm used to do in SVN.[...]Maybe we should try to stabilize the current patch before I star to mess around with GitHUB, I can try to isolate the stuff into smaller and more defined patches or do we want things forked first? How does it work on gitHub, should I create patches or just announce a revision for review?
QuoteIn order to integrate changes on github to our svn, we (I ?) have to create ordinary patch files, apply them to the svn working copy, commit there.
Quote from: sdog on November 07, 2013, 06:12:21 PMFor this topic perception seems to be mostly determined by the OS used. To Linux users git might look much easier than for windows users. (I often fall back on gitg, a GUI git manager.) On Linux SVN appears to require quite a bit of knowledge of the repository's structure, and some experience to configure it properly while git is a bit fire and forget, works out of the box and one can learn it while using. This seems to be very much different on windows.(Since it us so convenient to use for me it replaced most other method I used for syncing, except basic rsync.)
QuoteNo, Mercurial still doesn't support transcoding of filenames. That is, it will checkin and checkout filenames as binary strings and you will experience problems if you need to move files between systems with incompatible filename encodings.[...]There is a Windows UTF-8 plan in the works, and FUJIWARA Katsunori has been working on it, but it's not yet (September 2012) ready.
Quote from: sdog on November 08, 2013, 05:35:15 PM@mod or Igor: I've pushed the thread so far astray, it might be prudent to move it to randomness lounge. #9 would be a good break. I suppose Ters wouldn't mind.
Quote from: prissi on November 22, 2013, 10:29:44 PMI am not afraid of typing commands, as long as there is a way to memorize them without knots left in my brain ...
Quotegit is full of strange commands (like "git checkout -- file" to reset a file to its unmodified state) or things like fetch and merge (does anybody only do the first, and how do the last without the first). Also it was impossible to get github create a patch that was usuable with the commong patch tool.
QuoteWhen I have time, I will try mercurial, as it seems I cannot get warm with git.
QuoteIf you have never used version revision systems, your probably better start with git.
Quote from: sdog on November 22, 2013, 11:53:55 PMIs there a good shell with syntax completion available for windows? zsh does most of the remembering for me. (i couldn't get myself to remember git reset --hard or git checkout --hard HEAD~1)
Quote from: sdog on November 22, 2013, 11:53:55 PMespecially, with regard to branching, and working on the same thing on several computers, ie commiting changes in parallel, or unfinished work) In git when i started on monday A on my notebook, didn't finish, then did B in the office on tuesday and pushed it. On wednesday i would just stash the changes A on my notebook, pull B, apply the stashed A again and continue where i stopped on monday. That way i got 430 commits, when writing a 4 page paper (over the course of one year)...
C:\code\gitHub\base\simutrans [master]> git pull https://github.com/nikai3d/simutrans patch-1From https://github.com/nikai3d/simutrans * branch patch-1 -> FETCH_HEADMerge made by the 'recursive' strategy. readme.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)C:\code\gitHub\base\simutrans [master]> git pushremote: Permission to aburch/simutrans.git denied to Markohs.fatal: unable to access 'https://github.com/aburch/simutrans.git/': The requested URL returned error: 403