Hello,
S, after trying and trying I have finally came to a solution :)
My firewall from Comodo Internet Security suite was blocking ssh clients
somehow. Although I have no idea why and how because I can successfully
connect to other machine via SSH.
Now I will have to find a new
On Wednesday, July 18, 2012 3:47:14 PM UTC+2, Gabby Romano wrote:
Hi - I would like to move from svn to git. i would like to start from a
certain branch on svn and look back on trunk 1 year or so and start the
import from there.
I am using git-svn tool. the thing is that when I did that, I
git stash does not seem to handle symlinks to dirs. here is a simple demo:
$ ls dir1
f1
$ rm -rf dir1;ln -s dir2 dir1;git stash
error: 'dir1/f1' is beyond a symbolic link
fatal: Unable to process path dir1/f1
Cannot save the current worktree state
Is this a known issue? Is there a way around
Hello,
I apologize if this is a repeat post, but I haven't been able to find this
issue referenced. I'm running git on Ubuntu 12.04. Most of the commands work
fine, but I'm having trouble with git diff displaying any output. If I run:
$ git diff
$
on a repo that definitely has changes, I do
On Wed, Jul 18, 2012 at 04:10:19PM -0700, Bart Baker wrote:
I apologize if this is a repeat post, but I haven't been able to find this
issue referenced. I'm running git on Ubuntu 12.04. Most of the commands work
fine, but I'm having trouble with git diff displaying any output. If I run:
$
We're starting a new project and will be using git for our source code
management system. We're all previous SVN users and have not used git
before. I'm sure this question has been asked many times before and I
apologize for asking it again: What is the convention for setting up a new
project
first I used the regular git svn clone command - git svn clone svn path.
then tried with -rrev num:HEAD but that didn't work for me
either. probably tried a few more options but to no avail. I am sure git
knows how to follow the history despite the branching but didn't find the
right way to do it.
Note that git-svn will not follow history outside the paths you specify for
it. I believe it is restricted to a trunk and branches in a set location.
If at some point, the whole trunk/branches/tags was moved to a different
place in the repository, you have to splice together two git-svn clones
