[adding Konstantin]
Hu Haowen <[email protected]> writes:
> The content of zh_TW was too outdated comparing to the original files.
> Consequently carry out improvements in order to both keep track of sources
> and fix several grammatical mistakes in traditional Chinese.
>
> This is a thorough rewrite of the previous patch:
> https://lore.kernel.org/linux-doc/[email protected]/
> in order to get rid of text damage and merging errors, created based on
> linux-next (date: Oct. 9, 2023).
>
> Signed-off-by: Hu Haowen <[email protected]>
So this patch still isn't showing up in lore, with the result that b4
will not work with it. The thing is, it *does* make it through vger,
and has landed in the LWN archive:
https://lwn.net/ml/linux-kernel/20231010050727.49212-1-src.res.211%40gmail.com/
Might lore be dropping it because it consists of one big attachment?
Putting your patches inline would be the right thing to do in any case.
Rather than force another round, I've tried to the patch directly (but
see below), but it would be good to figure out why lore doesn't like it.
Konstantin, any ideas?
[Hmm...even weirder...v2, sent on Sep 25, wasn't in lore when I looked
on October 3 - but it *is* there now:
https://lore.kernel.org/lkml/[email protected]/
I'll admit to being entirely confused.]
The patch itself adds a whole bunch of new warnings, appended below, so
I've unapplied it again. We have been through a few too many rounds on
this, please do not resend until you have verified that it applies and
builds correctly.
Thanks,
jon
New warnings:
Documentation/translations/zh_TW/arch/index.rst:8: WARNING: toctree contains reference to nonexisting document 'translations/zh_TW/riscv/index'
Documentation/translations/zh_TW/arch/loongarch/introduction.rst:325: WARNING: duplicate label loongarch-references-zh_cn, other instance in Documentation/translations/zh_CN/arch/loongarch/introduction.rst
Documentation/translations/zh_TW/process/embargoed-hardware-issues.rst:25: WARNING: duplicate label zh_contact, other instance in Documentation/translations/zh_CN/process/embargoed-hardware-issues.rst
Documentation/translations/zh_TW/process/submitting-patches.rst:54: WARNING: duplicate label zh_describe_changes, other instance in Documentation/translations/zh_CN/process/submitting-patches.rst
Documentation/translations/zh_TW/process/submitting-patches.rst:137: WARNING: duplicate label zh_split_changes, other instance in Documentation/translations/zh_CN/process/submitting-patches.rst
Documentation/translations/zh_TW/process/submitting-patches.rst:270: WARNING: duplicate label zh_resend_reminders, other instance in Documentation/translations/zh_CN/process/submitting-patches.rst
Documentation/translations/zh_TW/process/submitting-patches.rst:451: WARNING: duplicate label zh_the_canonical_patch_format, other instance in Documentation/translations/zh_CN/process/submitting-patches.rst
Documentation/translations/zh_TW/process/submitting-patches.rst:556: WARNING: duplicate label zh_backtraces, other instance in Documentation/translations/zh_CN/process/submitting-patches.rst
Documentation/translations/zh_TW/process/submitting-patches.rst:575: WARNING: duplicate label zh_explicit_in_reply_to, other instance in Documentation/translations/zh_CN/process/submitting-patches.rst
On Tue, Oct 10, 2023 at 01:07:17PM -0600, Jonathan Corbet wrote:
> > This is a thorough rewrite of the previous patch:
> > https://lore.kernel.org/linux-doc/[email protected]/
> > in order to get rid of text damage and merging errors, created based on
> > linux-next (date: Oct. 9, 2023).
> >
> > Signed-off-by: Hu Haowen <[email protected]>
>
> So this patch still isn't showing up in lore, with the result that b4
> will not work with it. The thing is, it *does* make it through vger,
> and has landed in the LWN archive:
>
> https://lwn.net/ml/linux-kernel/20231010050727.49212-1-src.res.211%40gmail.com/
>
> Might lore be dropping it because it consists of one big attachment?
There's a moderation queue on lore for lists that aren't going through
subspace, and this patch was stuck there. The queue does get reviewed once
every 2-3 days, which explains why the others showed up, but with delay.
> Putting your patches inline would be the right thing to do in any case.
I'm not sure if your client is showing it differently, but to me the patch
appears to be just like any other -- it's inline and properly formed.
> Rather than force another round, I've tried to the patch directly (but
> see below), but it would be good to figure out why lore doesn't like it.
> Konstantin, any ideas?
If you like, we can migrate linux-doc to the new infrastructure and then you
will probably see it on lore faster than it's delivered into your inbox. :)
Either way, b4 should properly find and "am" it now.
-K
Konstantin Ryabitsev <[email protected]> writes:
>> Putting your patches inline would be the right thing to do in any case.
>
> I'm not sure if your client is showing it differently, but to me the patch
> appears to be just like any other -- it's inline and properly formed.
OK, weird...looking at the raw message it's definitely inline; no idea
why notmuch is showing it as an attachment.
>> Rather than force another round, I've tried to the patch directly (but
>> see below), but it would be good to figure out why lore doesn't like it.
>> Konstantin, any ideas?
>
> If you like, we can migrate linux-doc to the new infrastructure and then you
> will probably see it on lore faster than it's delivered into your inbox. :)
Sure, I'd be happy to see it move anytime.
Thanks,
jon