From: Markus Heidelberg <markus.heidelberg@web.de>
To: Elijah Newren <newren@gmail.com>, Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [filter-repo PATCH] convert-svnexternals: fix parsing of wrongly transformed SVN revisions
Date: Thu, 13 Apr 2023 15:59:53 +0200 [thread overview]
Message-ID: <12097307.TzdMVdA1NY@evo> (raw)
In-Reply-To: <xmqqbkjs9a1j.fsf@gitster.g>
Am Mittwoch, 12. April 2023, 21:26:32 CEST schrieb Junio C Hamano:
> It may work around the issue, but sounds like it is SubGit that
> needs fixing, at least seeing the problem description from the
> sideline.
Indeed the commit log should have been something like
"work around wrongly transformed SVN revisions"
to make it clear that it wasn't a bug in the script.
Thanks to your comment I have now reported this SubGit issue in the
TMate Support Forum.
prev parent reply other threads:[~2023-04-13 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 13:41 [filter-repo PATCH] convert-svnexternals: fix parsing of wrongly transformed SVN revisions Markus Heidelberg
2023-04-12 15:45 ` Elijah Newren
2023-04-12 19:26 ` Junio C Hamano
2023-04-13 13:59 ` Markus Heidelberg [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=12097307.TzdMVdA1NY@evo \
--to=markus.heidelberg@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@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).