From: Eric Wong <e@80x24.org>
To: Pavel Dydyshko via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Pavel Dydyshko <paul.dydyshko@gmail.com>
Subject: Re: [PATCH] svn: fix path strip for branches
Date: Thu, 6 Nov 2025 19:23:47 +0000 [thread overview]
Message-ID: <20251106192347.M949304@dcvr> (raw)
In-Reply-To: <pull.2087.git.git.1761917181558.gitgitgadget@gmail.com>
Pavel Dydyshko via GitGitGadget <gitgitgadget@gmail.com> wrote:
> perl/Git/SVN/Fetcher.pm | 4 ++++
> 1 file changed, 4 insertions(+)
Can you please include tests for this and your other change
for multi-line support in
<pull.2091.git.git.1761917197824.gitgitgadget@gmail.com>?
It's difficult to do any maintainence or updates on `git svn'
without tests, especially since SVN is far less common nowadays
with few remaining users. Thanks.
prev parent reply other threads:[~2025-11-06 19:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 13:26 [PATCH] svn: fix path strip for branches Pavel Dydyshko via GitGitGadget
2025-11-06 19:23 ` Eric Wong [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=20251106192347.M949304@dcvr \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=paul.dydyshko@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 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).