From: Junio C Hamano <gitster@pobox.com>
To: Joel Holdsworth <jholdsworth@nvidia.com>
Cc: git@vger.kernel.org, Luke Diamand <luke@diamand.org>,
Tzadik Vanderhoof <tzadik.vanderhoof@gmail.com>,
Dorgon Chang <dorgonman@hotmail.com>,
Joachim Kuebart <joachim.kuebart@gmail.com>,
Daniel Levin <dendy.ua@gmail.com>,
Johannes Schindelin <johannes.schindelin@gmx.de>,
Ben Keene <seraphire@gmail.com>,
Andrew Oakley <andrew@adoakley.name>
Subject: Re: [PATCH v2 RESEND 0/5] git-p4: fix RCS keyword processing encoding errors
Date: Tue, 04 Jan 2022 13:47:45 -0800 [thread overview]
Message-ID: <xmqqh7ajb2bi.fsf@gitster.g> (raw)
In-Reply-To: <20220104124913.2894-1-jholdsworth@nvidia.com> (Joel Holdsworth's message of "Tue, 4 Jan 2022 12:49:08 +0000")
Joel Holdsworth <jholdsworth@nvidia.com> writes:
> This patch-set fixes a family of issues with git-p4's handling of
> incoming text data that contains RCS keywords, when those files contain
> bytes which are invalid UTF-8 codes.
I do not see any difference between this version and what has been
merged to 'next' at 650cb248 (2021-12-27). Sent a wrong version?
In any case, if there is an update, since the original series is in
'next', please send in incremental changes on top of them.
Thanks.
next prev parent reply other threads:[~2022-01-04 21:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 12:49 [PATCH v2 RESEND 0/5] git-p4: fix RCS keyword processing encoding errors Joel Holdsworth
2022-01-04 12:49 ` [PATCH v2 RESEND 1/5] git-p4: use with statements to close files after use in patchRCSKeywords Joel Holdsworth
2022-01-04 12:49 ` [PATCH v2 RESEND 2/5] git-p4: pre-compile RCS keyword regexes Joel Holdsworth
2022-01-04 12:49 ` [PATCH v2 RESEND 3/5] git-p4: add raw option to read_pipelines Joel Holdsworth
2022-01-04 12:49 ` [PATCH v2 RESEND 4/5] git-p4: open temporary patch file for write only Joel Holdsworth
2022-01-04 12:49 ` [PATCH v2 RESEND 5/5] git-p4: resolve RCS keywords in bytes not utf-8 Joel Holdsworth
2022-01-04 21:47 ` Junio C Hamano [this message]
2022-01-04 21:59 ` [PATCH v2 RESEND 0/5] git-p4: fix RCS keyword processing encoding errors Joel Holdsworth
2022-01-04 22:48 ` Junio C Hamano
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=xmqqh7ajb2bi.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=andrew@adoakley.name \
--cc=dendy.ua@gmail.com \
--cc=dorgonman@hotmail.com \
--cc=git@vger.kernel.org \
--cc=jholdsworth@nvidia.com \
--cc=joachim.kuebart@gmail.com \
--cc=johannes.schindelin@gmx.de \
--cc=luke@diamand.org \
--cc=seraphire@gmail.com \
--cc=tzadik.vanderhoof@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).