From: Lukas Pupka-Lipinski <lukas.pupkalipinski@lpl-mind.de>
To: e@80x24.org
Cc: git@vger.kernel.org, pjwhams@gmail.com, normalperson@yhbt.net
Subject: [PATCH] added: Multi line support for ignore-paths configuration
Date: Wed, 25 Mar 2020 07:56:31 +0100 [thread overview]
Message-ID: <e5c78a24-e17f-c1bb-4ea7-3ddaa45abcf0@lpl-mind.de> (raw)
From 01d4e4dbc4e524db6188f41904a7274d1582d066 Mon Sep 17 00:00:00 2001
From: lukas.pupkalipinski@lpl-mind.de
Date: Tue, 24 Mar 2020 13:47:27 +0100
Subject: [PATCH] added: Multi line support for ignore-paths configuration
In addition we should add multi line support for include-paths.
Signed-off-by: lukas.pupkalipinski@lpl-mind.de
Reported-by:
Acked-by:
Reviewed-by:
Tested-by:
---
perl/Git/SVN/Fetcher.pm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/perl/Git/SVN/Fetcher.pm b/perl/Git/SVN/Fetcher.pm
index 64e900a0e9..1bcba49a76 100644
--- a/perl/Git/SVN/Fetcher.pm
+++ b/perl/Git/SVN/Fetcher.pm
@@ -31,7 +31,8 @@ sub new {
# override options set in an [svn-remote "..."] section
$repo_id = $git_svn->{repo_id};
my $k = "svn-remote.$repo_id.ignore-paths";
- my $v = eval { command_oneline('config', '--get', $k) };
+ my $v = eval { command('config', '--get-all', $k) };
+ $v =~ s/[\x0A\x0D]//g if (defined $v);
$self->{ignore_regex} = $v;
$k = "svn-remote.$repo_id.include-paths";
--
2.25.1.windows.1
next reply other threads:[~2020-03-25 7:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 6:56 Lukas Pupka-Lipinski [this message]
2020-03-25 20:38 ` [PATCH] added: Multi line support for ignore-paths configuration Eric Wong
2020-03-25 21:24 ` Junio C Hamano
[not found] ` <0515a11b-d9ae-3f22-65a8-5efee235d5c9@lpl-mind.de>
2020-03-29 23:24 ` Eric Wong
[not found] ` <8fbfbf1c-ea14-6739-7881-cfa3d9642de9@lpl-mind.de>
2020-04-13 18:18 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5c78a24-e17f-c1bb-4ea7-3ddaa45abcf0@lpl-mind.de \
--to=lukas.pupkalipinski@lpl-mind.de \
--cc=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=pjwhams@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).