From: Junio C Hamano <junio@pobox.com>
To: Heikki Orsila <heikki.orsila@iki.fi>
Cc: git@vger.kernel.org, Miklos Vajna <vmiklos@frugalware.org>
Subject: Re: [PATCH] Add SVN->Git conversion example to documentation
Date: Tue, 17 Jun 2008 16:21:36 -0700 [thread overview]
Message-ID: <7viqw74phb.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080614215812.GA28574@zakalwe.fi> (Heikki Orsila's message of "Sun, 15 Jun 2008 00:58:12 +0300")
Heikki Orsila <heikki.orsila@iki.fi> writes:
> Signed-off-by: Heikki Orsila <heikki.orsila@iki.fi>
> ---
> This is the third round. Added some commands to clean up the repository,
> and set fetch heads. Thanks to Miklos Vajna for feedback.
>
> Documentation/git-svn.txt | 41 ++++++++++++++++++++++++++++++++++++++---
> 1 files changed, 38 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
> index f4cbd2f..26e00c5 100644
> --- a/Documentation/git-svn.txt
> +++ b/Documentation/git-svn.txt
> @@ -11,9 +11,12 @@ SYNOPSIS
>
> DESCRIPTION
> -----------
> -git-svn is a simple conduit for changesets between Subversion and git.
> -It is not to be confused with linkgit:git-svnimport[1], which is
> -read-only.
> +git-svn is a simple bidirectional conduit for changesets between
> +Subversion and git. It is used to develop projects with Git tools,
> +but commit changes to a Subversion repository. It can also be used to
That is correct but doesn't the above give a false impression that commits
are only made on subversion side and never on git side?
> +convert a Subversion repository to a Git repository. It should not
> +be confused with linkgit:git-svnimport[1], which does Subversion to
> +Git conversion, but not the other direction.
We do not ship nor document svnimport anymore and linkgit: there is
actively wrong. People seem to be confused with ancient documents still
floating on the Web that talk about svnimport, and I think it is a good
idea to try to clear the confusion here, but perhaps...
... with the deprecated `git-svnimport`, which was used for
one-way conversion from Subversion to git.
> @@ -520,6 +523,38 @@ have each person clone that repository with 'git clone':
> git-svn rebase
> ------------------------------------------------------------------------
>
> +CONVERTING A SUBVERSION REPOSITORY TO A GIT REPOSITORY
> +------------------------------------------------------
> +
> +When converting a Subversion repository to a Git repository
> +--no-metadata removes "git-svn-id:" comments from the log.
> +-A option is used to convert SVN pseudonyms to real names
Anything that user usually would type on the command line it is preferred
to typeset with `quoted like this`, so "`--no-metadata`" and "`-A` option".
It is not `--no-metadata` "removes". git-svn adds cruft because it wants
to use it for bidi operation, but --no-metadata prevents it from doing
so.
next prev parent reply other threads:[~2008-06-17 23:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 21:58 [PATCH] Add SVN->Git conversion example to documentation Heikki Orsila
2008-06-14 22:47 ` Miklos Vajna
2008-06-17 23:21 ` Junio C Hamano [this message]
2008-06-18 0:55 ` Heikki Orsila
-- strict thread matches above, loose matches on Subject: below --
2008-06-14 18:09 Heikki Orsila
2008-06-14 19:06 ` Miklos Vajna
2008-06-14 21:50 ` Heikki Orsila
2008-06-14 18:03 Heikki Orsila
2008-06-15 13:17 ` Karl Hasselström
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7viqw74phb.fsf@gitster.siamese.dyndns.org \
--to=junio@pobox.com \
--cc=git@vger.kernel.org \
--cc=heikki.orsila@iki.fi \
--cc=vmiklos@frugalware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.