We also use a -depth=1 so it takes less space on tmp dirs. git svn can track a standard Subversion repository, following the common 'trunk/branches/tags' layout, with the -stdlayout option. It provides a bidirectional flow of changes between a Subversion and a Git repository.
git directory contents will end up in a tmp dir. Clones a repository into a newly created directory, creates remote-tracking branches for each branch in the cloned repository (visible using git branch -remotes ), and creates and checks out an initial branch that is forked from the cloned repository’s currently active branch. DESCRIPTION git svn is a simple conduit for changesets between Subversion and Git. git file (not a directory) whose content will be a single line: gitdir: īecause we used a tmp dir with the mktemp command, the actual. The -separate-git-dir flag lets you specify a path for the. Git clone -separate-git-dir=$(mktemp -u) -depth=1 $dir & rm $dir/.git In zsh, I made that a function so I ensure a dir value is defined: alias np='node-project' We can either checkout the tag in the Detached HEAD state or we can create a new branch. It has a dependency on mktemp command so it'll work *nix systems (from what I see this needs further work for the mktemp to work on MacOS, so if anyone wants to comment a working solution I'll add it) We can checkout or navigate to a tag by using the Git Checkout command. git file, which means it could never accidentally rm -rf a wrong.
I like this solution more because I don't like rm -rfing things automatically. Git clone -separate-git-dir=$(mktemp -u) -depth=1 & rm /.git
0 kommentar(er)
