git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tor Arntsen <tor@spacetec.no>
To: Marin Atanasov <dnaeon@gmail.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>, git@vger.kernel.org
Subject: Re: Git and cvsimport
Date: Tue, 27 Apr 2010 13:58:01 +0200	[thread overview]
Message-ID: <r2xd2d39d861004270458v2e1cb73by78f53d71103b47e6@mail.gmail.com> (raw)
In-Reply-To: <l2w717f7a3e1004270341lea6cfe2aqdf8d2b490b1ec067@mail.gmail.com>

On Tue, Apr 27, 2010 at 12:41, Marin Atanasov <dnaeon@gmail.com> wrote:

> Perhaps I didn't explain better what I want to accomplish :)
>
> I want to convert CVS repo to a Git one.

But the above statement..
[..]
> What I want to do is to checkout from CVS the files which are tagged
> RELEASE_1_0 for example, and then import the files to a Git repo.
> Files tagged as RELEASE_1_0 differ from HEAD files, so I want only
> those files with that tag for example.

.. seems to be in conflict with the above paragraph. Files tagged with
RELEASE_1_0 sounds like a revision tag (i.e. not a branch). If you
want to checkout that snapshot and insert into a Git rep you could as
well just 'cvs export -r RELEASE_1_0 <module>; git init; git add .;
git commit'
but that obviously won't give you any CVS history in the Git repo.

Is RELEASE_1_0 instead a branch tag? I.e. a CVS branch?

-Tor

  parent reply	other threads:[~2010-04-27 11:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 14:27 Git and cvsimport Marin Atanasov
2010-04-27  7:37 ` Michael J Gruber
2010-04-27 10:41   ` Marin Atanasov
2010-04-27 11:03     ` Michael J Gruber
2010-04-27 11:57     ` Nick
2010-04-27 11:58     ` Tor Arntsen [this message]
2010-04-28  5:27       ` Marin Atanasov Nikolov
2010-04-28  9:19         ` Andreas Schwab

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=r2xd2d39d861004270458v2e1cb73by78f53d71103b47e6@mail.gmail.com \
    --to=tor@spacetec.no \
    --cc=dnaeon@gmail.com \
    --cc=git@drmicha.warpmail.net \
    --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).