From: David Brown <git@davidb.org>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: binary safe?
Date: Fri, 4 Nov 2005 13:27:01 -0800 [thread overview]
Message-ID: <20051104212701.GA4310@old.davidb.org> (raw)
In-Reply-To: <46a038f90511041322x1d9f7a50ndafe724c2e8d368b@mail.gmail.com>
On Sat, Nov 05, 2005 at 10:22:29AM +1300, Martin Langhoff wrote:
> (That being said, if you have a case where git-cvsimport is doing the
> wrong thing, let me know!)
>
> > However, since CVS (RCS really) can remember the state of this flag, it
> > does work to 'cvs admin -ko filename' beforehand, and then do the
> > cvsimport without the '-k' option.
>
> Yes, but a repo you don't control, where people are using keywords,
> means thatyou need to do -kk to kill the keywords or your imported
> files are going to have a horrid amount of noise in them.
Yes, the unpleasantness of CVS.
However, I was unable to do a proper git-cvsimport of the SourceForge 'vim'
archive, with '-k'. By not giving it '-k' and using cvs admin '-ko' on the
appropriate files, I was able to get the correct results.
May be the interpretation of the option depends on the particular server
being used?
I can investigate later which particular file is causing the problem.
Dave
next prev parent reply other threads:[~2005-11-04 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 22:02 binary safe? Randal L. Schwartz
2005-11-03 22:49 ` Junio C Hamano
2005-11-03 23:00 ` Martin Langhoff
2005-11-04 16:54 ` David Brown
2005-11-04 21:22 ` Martin Langhoff
2005-11-04 21:27 ` David Brown [this message]
2005-11-03 22:50 ` Linus Torvalds
2005-11-04 3:49 ` Chris Wedgwood
2005-11-03 23:05 ` Nick Hengeveld
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=20051104212701.GA4310@old.davidb.org \
--to=git@davidb.org \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
/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.