git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacob Helwig <jacob.helwig@gmail.com>
To: "fkater@googlemail.com" <fkater@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: migrating to git: keep subversion revision numbers (as tags?)
Date: Sat, 30 Jan 2010 15:36:14 -0800	[thread overview]
Message-ID: <8c9a061001301536g1a990881qa27ba681ee90c6eb@mail.gmail.com> (raw)
In-Reply-To: <20100130230829.GA3544@comppasch2>

On Sat, Jan 30, 2010 at 15:08, fkater@googlemail.com
<fkater@googlemail.com> wrote:
> Hi,
>
> I would like to completely migrate from subversion to git
> (and NOT have subversion enabled anymore). However, I need
> to be able to lookup the old subversion revision numbers
> later from the git repository. The default seems to be
> though, that they are replaced by git sha-1 keys.
>
> It would be completely o.k. here to use git tags for all
> those subversion revision numbers (if possible), so, to
> create a tag for each subversion revision. However, I have
> neither seen any option in git nor found a script which does
> that upon cloning (converting) a subversion repo into a git
> repo.
>
> Is there a way to do so?
>
> Thank You
>  Felix
>

There's not really any need to tag every revision with the SVN
revision number.  If you use svn-all-fast-export, or git-svn to do the
SVN -> Git conversion, then the SVN revision numbers will end up as
part of the commit message when it is in Git.

-Jacob

  parent reply	other threads:[~2010-01-30 23:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-30 23:08 migrating to git: keep subversion revision numbers (as tags?) fkater
2010-01-30 23:35 ` Jon Seymour
2010-01-30 23:36 ` Jacob Helwig [this message]
2010-01-31  8:04 ` Ilari Liusvaara

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=8c9a061001301536g1a990881qa27ba681ee90c6eb@mail.gmail.com \
    --to=jacob.helwig@gmail.com \
    --cc=fkater@googlemail.com \
    --cc=git@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).