From: Ralf Baechle <ralf@uni-koblenz.de>
To: Andrew Linfoot <andy@derfel99.freeserve.co.uk>
Cc: linux <linux@cthulhu.engr.sgi.com>
Subject: Re: CVS Woes
Date: Mon, 28 Jun 1999 03:06:12 +0200 [thread overview]
Message-ID: <19990628030612.A730@uni-koblenz.de> (raw)
In-Reply-To: <001401bec0eb$87774220$0a02030a@snafu>; from Andrew Linfoot on Sun, Jun 27, 1999 at 11:22:21PM +0100
On Sun, Jun 27, 1999 at 11:22:21PM +0100, Andrew Linfoot wrote:
>
> DEC Alpha running NT and Internal modem
> samba share on my indy source tree
>
> I can connect to cvs@linus and do a cvs update. The problem is that samba or
> cvs appears to be converting the files to the DOS CR/LF format! and then
> everything breaks horribly.
>
> How can i get around this?
What CVS is doing is correct, it converts the files into what the local
system - the NT system - is using.
As a workaround try the keyword expansion mode -kb when checking out.
That will give you the original context of the server which happens to be
just right for your Indy.
> Anyone got a script or something that will strip this crap out!
Use find(1) and tr(1). Or recode ...
Ralf
prev parent reply other threads:[~1999-06-28 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-27 22:22 CVS Woes Andrew Linfoot
1999-06-28 1:06 ` Ralf Baechle [this message]
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=19990628030612.A730@uni-koblenz.de \
--to=ralf@uni-koblenz.de \
--cc=andy@derfel99.freeserve.co.uk \
--cc=linux@cthulhu.engr.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox