git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Markus Heidelberg <markus.heidelberg@web.de>, git@vger.kernel.org
Subject: Re: [filter-repo PATCH] convert-svnexternals: fix parsing of wrongly transformed SVN revisions
Date: Wed, 12 Apr 2023 12:26:32 -0700	[thread overview]
Message-ID: <xmqqbkjs9a1j.fsf@gitster.g> (raw)
In-Reply-To: <CABPp-BH1172tfZn5i0PvNm6Fw5OObKEKCqT1gjTr+hux86TexQ@mail.gmail.com> (Elijah Newren's message of "Wed, 12 Apr 2023 08:45:04 -0700")

Elijah Newren <newren@gmail.com> writes:

> Thanks for sending this in!  Applied.

It may work around the issue, but sounds like it is SubGit that
needs fixing, at least seeing the problem description from the
sideline.

  reply	other threads:[~2023-04-12 19:26 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 [this message]
2023-04-13 13:59     ` Markus Heidelberg

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=xmqqbkjs9a1j.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=markus.heidelberg@web.de \
    --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).