From: Erik Faye-Lund <kusmabite@googlemail.com>
To: git@vger.kernel.org
Cc: normalperson@yhbt.net, dpotapov@gmail.com
Subject: [PATCH 3/3] Revert "git-svn: always initialize with core.autocrlf=false"
Date: Wed, 3 Mar 2010 21:10:23 +0100 [thread overview]
Message-ID: <1267647023-2604-3-git-send-email-kusmabite@gmail.com> (raw)
In-Reply-To: <1267647023-2604-1-git-send-email-kusmabite@gmail.com>
git-svn rebase used to have issues with CRLF conversion. Since these issues
have been fixed, we can safely revert the work-around that disables CRLF
conversion.
This reverts commit d3c9634eacdcaa71cbd69a160e6f4e80ddb7ab63.
Signed-off-by: Erik Faye-Lund <kusmabite@gmail.com>
---
git-svn dcommit uses diff-tree (which does not apply CRLF conversion) to
generate SVN commits, so there never were any CRLF conversion issues when
commiting in the first place.
git-svn.perl | 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/git-svn.perl b/git-svn.perl
index b7c03b6..b8a3fc2 100755
--- a/git-svn.perl
+++ b/git-svn.perl
@@ -369,7 +369,6 @@ sub do_git_init_db {
command_noisy(@init_db);
$_repository = Git->repository(Repository => ".git");
}
- command_noisy('config', 'core.autocrlf', 'false');
my $set;
my $pfx = "svn-remote.$Git::SVN::default_repo_id";
foreach my $i (keys %icv) {
--
1.7.0.1.141.gc5984a
next prev parent reply other threads:[~2010-03-03 20:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 20:10 [PATCH 1/3] hash-object: support --stdin-paths with --no-filters Erik Faye-Lund
2010-03-03 20:10 ` [PATCH 2/3] git-svn: support fetch with autocrlf on Erik Faye-Lund
2010-03-03 20:10 ` Erik Faye-Lund [this message]
2010-03-03 20:16 ` [PATCH 3/3] Revert "git-svn: always initialize with core.autocrlf=false" Erik Faye-Lund
2010-03-04 9:53 ` Eric Wong
2010-03-04 10:24 ` Erik Faye-Lund
2010-03-04 14:35 ` [PATCH 1/3] hash-object: support --stdin-paths with --no-filters Dmitry Potapov
2010-03-04 18:11 ` Junio C Hamano
2010-03-05 11:05 ` Eric Wong
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=1267647023-2604-3-git-send-email-kusmabite@gmail.com \
--to=kusmabite@googlemail.com \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/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).