git-svn

问题 Continuing from my previous question I decided to go ahead and reclone the thing : $ git svn clone --branches=Branches/Wrye\ Bash/* \ --tags=Tags/Wrye\ Bash/* \ --trunk=Programs/Wrye\ Bash/ --prefix=svn/ \ --ignore-paths="^(?:Releases|Projects|Scripts|Games|)/|^Programs/\ (?:Nif Scanner|Nif Viewer|Raziel23x's Oblivion Toolset|Shader Disasm|Shader Editor)/" \ --authors-file=authors_with_emails.txt \ svn://svn.code.sf.net/p/oblivionworks/code/ . >> 2013.07.28 2>&1 So now I only cloned a

问题 I cloned an svn repo with git svn clone ... and now I want to push changes to it. after that I will use this repo to rebase everything and commit back to svn. The problem that pushing to a non-bare repo seems to not be a good idea, and git svn seems unhappy about working with a bare one? 回答1: You can always use an intermediate bare repo. After all, pushing to a repo with which you work is not a good idea. You can also pull to it instead of pushing if this option is available. 来源： https:/

问题 I cloned an svn repo with git svn clone ... and now I want to push changes to it. after that I will use this repo to rebase everything and commit back to svn. The problem that pushing to a non-bare repo seems to not be a good idea, and git svn seems unhappy about working with a bare one? 回答1: You can always use an intermediate bare repo. After all, pushing to a repo with which you work is not a good idea. You can also pull to it instead of pushing if this option is available. 来源： https:/

问题 When using git svn, a sparse checkout of the central repository may be achieved by something along the lines of git clone -s URL-to-root --include-paths 'dir1|dir2|dir3' After using this setup for some time, I would like to add another directory dir4 to those tracked. This directory has existed in many commits that I have already checked out. Editing the variable svn-remote.svn.include-paths by running git config --edit does not have the desired effect on git fetch (only files changed in

问题 When using git svn, a sparse checkout of the central repository may be achieved by something along the lines of git clone -s URL-to-root --include-paths 'dir1|dir2|dir3' After using this setup for some time, I would like to add another directory dir4 to those tracked. This directory has existed in many commits that I have already checked out. Editing the variable svn-remote.svn.include-paths by running git config --edit does not have the desired effect on git fetch (only files changed in

问题 I commit a few changes locally and then push to github using 'git push origin master'. It always pushes the complete code base (judging by the amount of data transferred). I must be missing something simple.. should only push up the changed files..? 回答1: That is a mystery to me too. My colleague has found that creating tracking branches helps: http://www.zorched.net/2008/04/14/start-a-new-branch-on-your-remote-git-repository/ EDIT I found that this happens when I don't pull before creating a

问题 I have a flat svn repository which looks like: my_repo/ ├── file1.c ├── file2.c ├── file3.c └── README This repo has no branches, or tags and all I am trying to do is convert it to a git repository and maintain the commit history. I have tried: git svn clone --trunk=/ -A users.txt svn+ssh://user@svn.example.com/projects/my_repo dest_dir Which I assumed would work, however, when I navigate into dest_dir and perform git svn fetch , it doesn't seem to fetch anything. Using git log yields: fatal:

问题 i am about to clone code from svn repo (on centos) using git svn clone -s svn://xxx, then it is interrupted for strange problems, the error message is as follows: Following parent with do_switch Successfully followed parent Use of uninitialized value in concatenation (.) or string at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/SVN/Core.pm line 584. Network connection closed unexpectedly: at /usr/libexec/git-core/git-svn line 2693 then i continue this clone process using time git

问题 Something strange happened when I ran git svn clone -s, though the following information tells us to not be alarmed, I wonder why that is kind of svn error? Why this path does not exist, is it deleted by others? If yes, why git svn should search aggressively for old history? Initializing parent: refs/remotes/tags/sequentialInformationalBottleneckClusterer-1.0.1@8400 W: Ignoring error from SVN, path probably does not exist: (160013): Filesystem has no item: File not found: revision 101, path '

问题 While trying to clone an existing Subversion repository using git-svn using standard layout, I got a bunch of W: -empty_dir (and W: +empty_dir ) warnings. The cloned git repository seems to be working, i.e. I can do usual git operations and dcommit to SVN repository. The real problem is that the initial clone and rebase create some empty directories that do not exist in SVN repository, at the top of the repository (along with other directories in trunk). These directories contain no file but