| Message ID | 20240206105246.1220945-6-buildroot@bubu1.eu |
|---|---|
| State | Accepted |
| Headers | show |
| Series | [1/6] utils/readme.txt: expand check-package description | expand |
Marcus, All, On 2024-02-06 11:52 +0100, Marcus Hoffmann via buildroot spake thusly: > Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu> > --- > docs/manual/contribute.adoc | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/docs/manual/contribute.adoc b/docs/manual/contribute.adoc > index 684e9f4809..7d0611be28 100644 > --- a/docs/manual/contribute.adoc > +++ b/docs/manual/contribute.adoc > @@ -375,6 +375,14 @@ If you do not use +git send-email+, make sure posted *patches are not > line-wrapped*, otherwise they cannot easily be applied. In such a case, > fix your e-mail client, or better yet, learn to use +git send-email+. > > +https://sr.ht also has a light-weight UI for > +https://man.sr.ht/git.sr.ht/#sending-patches-upstream[preparing patchseries] > +and can also send out the patches for you. There are a few drawbacks to > +this, as you cannot edit your patches' status in Patchwork and you > +currently can't edit your display name with which the match emails are > +sent out but it is an option if you cannot get git send-email to work > +with your mail provider (i.e. O365). As seen IRL, I extended that with a blurb explicitly stating that it's not the official way of sneding patches, just a fallback. Applied to master, thanks. Regards, Yann E. MORIN. > ==== Cover letter > > If you want to present the whole patch set in a separate mail, add > -- > 2.43.0 > > _______________________________________________ > buildroot mailing list > buildroot@buildroot.org > https://lists.buildroot.org/mailman/listinfo/buildroot
diff --git a/docs/manual/contribute.adoc b/docs/manual/contribute.adoc index 684e9f4809..7d0611be28 100644 --- a/docs/manual/contribute.adoc +++ b/docs/manual/contribute.adoc @@ -375,6 +375,14 @@ If you do not use +git send-email+, make sure posted *patches are not line-wrapped*, otherwise they cannot easily be applied. In such a case, fix your e-mail client, or better yet, learn to use +git send-email+. +https://sr.ht also has a light-weight UI for +https://man.sr.ht/git.sr.ht/#sending-patches-upstream[preparing patchseries] +and can also send out the patches for you. There are a few drawbacks to +this, as you cannot edit your patches' status in Patchwork and you +currently can't edit your display name with which the match emails are +sent out but it is an option if you cannot get git send-email to work +with your mail provider (i.e. O365). + ==== Cover letter If you want to present the whole patch set in a separate mail, add
Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu> --- docs/manual/contribute.adoc | 8 ++++++++ 1 file changed, 8 insertions(+)