From: Andreas Schwab <schwab@linux-m68k.org>
To: Ilya Basin <basinilya@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git cvsimport: new tags not imported on second cvsimport
Date: Sat, 04 Aug 2012 17:58:26 +0200 [thread overview]
Message-ID: <m2pq76vecd.fsf@igel.home> (raw)
In-Reply-To: <9510482012.20120804170149@gmail.com> (Ilya Basin's message of "Sat, 4 Aug 2012 17:01:49 +0400")
Ilya Basin <basinilya@gmail.com> writes:
> AS> Ilya Basin <basinilya@gmail.com> writes:
>
>>> I made the initial import:
>>> git cvsimport -d :pserver:user@blackbird:10010/data/cvs/webgui -C SAP -r cvs -k SAP
>>>
>>> edited .git/config:
>>> [cvsimport]
>>> module = SAP
>>> r = cvs
>>> d = :pserver:user@blackbird:10010/data/cvs/webgui
>>>
>>> did some commits to CVS and created a new tag
>>>
>>> Then ran:
>>> git cvsimport -ak
>>> To synchronize with CVS.
>>>
>>> The new commits were imported, but the new tag wasn't.
>
> AS> cvsimport never reconsiders changesets that were already imported, so if
> AS> the tag was added to such a changeset it won't be seen.
>
> AS> Andreas.
>
>
> Do you mean, if I tag BEFORE cvsimport, it will be imported?
If you tag one of the new commits it will be imported.
> How to make the git repo "forget" the last cvsimport?
Reset the branch back to before the import.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-08-04 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 9:31 git cvsimport: new tags not imported on second cvsimport Ilya Basin
2012-08-04 9:45 ` Andreas Schwab
2012-08-04 13:01 ` Re[2]: " Ilya Basin
2012-08-04 15:58 ` Andreas Schwab [this message]
2012-08-04 22:09 ` Junio C Hamano
2012-08-04 22:20 ` 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=m2pq76vecd.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=basinilya@gmail.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).