From: Heiko Voigt <hvoigt@hvoigt.net>
To: "Ferry Huberts (Pelagic)" <ferry.huberts@pelagic.nl>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Add warning about known issues to documentation of cvsimport
Date: Tue, 31 Mar 2009 00:17:29 +0200 [thread overview]
Message-ID: <20090330221729.GB68118@macbook.lan> (raw)
In-Reply-To: <49C7F233.9050205@pelagic.nl>
On Mon, Mar 23, 2009 at 09:33:55PM +0100, Ferry Huberts (Pelagic) wrote:
> maybe you can also add remarks about autocrlf and safecrlf?
> both need to be off
>From my experience thats not necessarily true. You can use
autocrlf=input to repair broken revisions were crlf's have been
mistakenly committed into the repository. And if I remember correctly
safecrlf helps if you want to make sure that no information gets lost.
So when importing from a nice correct cvs repository you would expect
safecrlf to not stop your import. And I suspect there are actually cvs
users that were very careful with their lineendings who would use it.
cheers Heiko
next prev parent reply other threads:[~2009-03-30 22:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 19:53 [PATCH] Add warning about known issues to documentation of cvsimport Heiko Voigt
2009-03-23 20:33 ` Ferry Huberts (Pelagic)
2009-03-30 22:17 ` Heiko Voigt [this message]
2009-03-31 5:36 ` Ferry Huberts (Pelagic)
2009-03-31 16:22 ` Heiko Voigt
2009-03-31 16:53 ` [PATCH] cvsimport: Add a note about crlf options to the documentation Heiko Voigt
2009-03-31 17:10 ` [PATCH] Add warning about known issues to documentation of cvsimport Ferry Huberts (Pelagic)
2009-03-24 3:14 ` Jeff King
2009-03-30 22:36 ` Heiko Voigt
2009-03-31 0:51 ` Junio C Hamano
2009-03-31 16:45 ` [PATCH] Cleanup warning about known issues in cvsimport documentation Heiko Voigt
2009-03-31 19:49 ` Jeff King
2009-04-01 20:24 ` [PATCH v2] " Heiko Voigt
2009-03-31 11:28 ` [PATCH] Add warning about known issues to documentation of cvsimport Jeff King
2009-03-31 19:40 ` Jeff King
2009-03-31 23:55 ` Junio C Hamano
2009-04-01 8:50 ` [PATCH] Documentation: use "spurious .sp" XSLT if DOCBOOK_SUPPRESS_SP is set Chris Johnsen
2009-04-01 10:14 ` Jeff King
2009-04-02 5:25 ` Junio C Hamano
2009-04-01 10:34 ` Jeff King
2009-04-01 12:19 ` Chris Johnsen
2009-04-01 13:06 ` Jeff King
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=20090330221729.GB68118@macbook.lan \
--to=hvoigt@hvoigt.net \
--cc=ferry.huberts@pelagic.nl \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).