...
This instructs git to clone the entire repository, including the complete revision history. This may take a while for repositories with a long history. You can use the -r option to request a partial history. From the man page:
| Code Block |
|---|
-r <ARG>, --revision <ARG> |
...
Used with the fetch command. |
...
This allows revision ranges for partial/cauterized history to be |
...
supported. $NUMBER, $NUMBER1:$NUMBER2 (numeric ranges), |
...
$NUMBER:HEAD, and BASE:$NUMBER are all supported. |
...
This can allow you to make partial mirrors when running fetch; but
is generally not recommended because history will be skipped and
lost.
git: Integrating w/ Subversion
This can allow you to make partial mirrors when running fetch; but
is generally not recommended because history will be skipped and
lost.
|
Committing your changes back to the Subversion repository:
| Code Block |
|---|
git svn dcommit |
Before you push your changes to the Subversion repository you need to first commit any pending modifications to your local repository. Otherwise, git will complain:
| Code Block |
|---|
$ git svn dcommit |
...
Cannot dcommit with a dirty index. Commit your changes first, or stash them with `git stash'. |
...
at /usr/libexec/git-core/git-svn line 491 |
To fix this, commit your changes:
| Code Block |
|---|
$ git commit -m 'a meaningful commit message' -a |
And then send your changes to the Subversion repository:
| Code Block |
|---|
$ git svn dcommit |
...
Committing to https://source.seas.harvard.edu/svn/version-control-workshop/trunk ... |
...
M seealso.rst |
...
Committed r38 |
...
M seealso.rst |
...
r38 = 03254f2c0b3d5e068a87566caef84454558b85b0 (refs/remotes/trunk) |
...
No changes between current HEAD and refs/remotes/trunk |
...
Resetting to the latest refs/remotes/trunk |
...
Unstaged changes after reset: |
...
M git.rst |
...
M git.rst |
...
Committed |
...
r39 M git.rst |
...
r39 = d1f884a3f945f6083541e28ab7a09ca8efc6343b (refs/remotes/trunk) |
...
No changes between current HEAD and refs/remotes/trunk |
...
Resetting to the latest refs/remotes/trunk |
git: Integrating w/ SubversionUpdating your working copy from the Subversion repository:
| Code Block |
|---|
git svn rebase |
As with git svn dcommit, you must have a clean working copy before running the rebase command. git:
Integrating w/ CVS
You can import a CVS repository into git (this is a one-time, one-way operation). The CVS import feature requires cvsps, a tool for collating CVS changes into changesets.
git: Integrating w/ CVS
This may take a while:
| Code Block |
|---|
export CVSHOME=:pserver:anonymous@example.com |
...
cvs login |
...
git cvsimport -o cvs_head -C my-project |
...
Git Frontends
The git wiki has a list of frontends for git.