Re: [PATCH v7 00/11] docs/zh_CN: add core api and openrisc translation

[teng sterling <sterlingteng@gmail.com>]

OK!
Maybe I misunderstood the patch split。~>_<~
And next time:
when I add a new file, I will do the associated index.rst changes in
the same patch.

Thanks,

Yanteng

Jonathan Corbet <corbet@lwn.net> 于2021年4月21日周三 上午6:11写道：
>
> Yanteng Si <siyanteng@loongson.cn> writes:
>
> > This series of patches translates core-api/irq/* and openrisc/* into Chinese.
> >
> > v1 -> v2:
> >
> > Modify some words under Xiangcheng Wu's suggestion. Thanks for his rewiew!
> >
> > v2 -> v3:
> >
> > keep the signs number equal to the title char under Alex's suggestion.
> > Thanks for his rewiew!
> >
> > v3 -> v4:
> >
> > Add Xiangcheng Wu's review sign to 0002、0003 and 0008; Thanks for his rewiew!
> >
> > v4 -> v5:
> >
> > Split 1-7 into a separate series.
> >
> > v5 -> v6:
> >
> > Modify the Subject of patches 07 and 11.
> > Patch 11 will not be sent if not modified. (name repeat)
> >
> > Revert to one series because there is no need to split into two series.
> >
> > v6 -> v7:
> >
> > Send patch 11 to the series. Thank you Xiangcheng for your help!
> >
> > Yanteng Si (11):
> >   docs/zh_CN: add core-api irq concepts.rst translation
> >   docs/zh_CN: add core-api irq irq-affinity.rst translation
> >   docs/zh_CN: add core-api irq irq-domain.rst translation
> >   docs/zh_CN: add core-api irq irqflags-tracing.rst translation
> >   docs/zh_CN: add core-api irq index.rst translation
> >   docs/zh_CN: add core-api index.rst translation
> >   docs/zh_CN: add core api translation to zh_CN index
> >   docs/zh_CN: add openrisc openrisc_port.rst translation
> >   docs/zh_CN: add openrisc todo.rst translation
> >   docs/zh_CN: add openrisc index.rst translation
> >   docs/zh_CN: add openrisc translation to zh_CN index
>
> I have applied this series, thanks.
>
> I have a request for the future, though: when you add a new file, do the
> associated index.rst changes *in the same patch*.  Among other things,
> that helps bisectability - we'll know which patch adds a build error,
> for example.  It's not hugely important for docs, but is a good way to
> approach kernel work in general - don't stack up lots of work that only
> becomes active as the result of a small patch at the end.
>
> THanks,
>
> jon