From: LIU Hao <lh_mouse@126.com>
To: Xi Ruoyao <xry111@xry111.site>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Adding a new thread model to GCC
Date: Tue, 4 Oct 2022 21:45:58 +0800 [thread overview]
Message-ID: <a23ad853-2cc7-63af-99e6-362ade66fcd8@126.com> (raw)
In-Reply-To: <8ccc48f13c385c6c3583cc9e63a09457163dcd23.camel@xry111.site>
[-- Attachment #1.1: Type: text/plain, Size: 2132 bytes --]
在 2022-10-04 21:13, Xi Ruoyao 写道:
>
> In GCC development we usually include the configure regeneration in the
> patch because the scripts are also version controlled.
>
There is a reason for not doing that: Generated contents can't be reviewed.
In mingw-w64 we do the opposite: The person who commits a patch is responsible for update configure,
Makefile.in, etc. The patch itself doesn't include generated contents.
> It's better to include the ID in the subject and ChangeLog of the patch.
> Like:
>
> [PATCH 1/3] libgfortran: Use `__gthread_t` instead of `pthread_t` [PR 105764]
>
> It used to cause errors if a thread model other than `posix` was selected,
> which looks like a leftover from a79878585a1c5e32bafbc6d1e73f91fd6e4293bf.
>
> libgfortran/ChangeLog:
>
> PR libgfortran/105764
> * io/async.h (struct async_unit): Use `__gthread_t` instead
> of `pthread_t`.
>
Yes I think this change is good.
>
> And, from https://gcc.gnu.org/contribute.html#patches:
>
> "It is strongly discouraged to post patches as MIME parts of type
> application/whatever, disposition attachment or encoded as base64 or
> quoted-printable."
>
> Just try "git send-email", it will do the correct thing. Mimicking its
> behavior in a mail client is also possible but error-prune (the mail
> client can destroy your patch by replacing your tabs with spaces, etc.)
>
It's 'discouraged'. It is not forbidden. I expect everywhere people who receive emails to accept
attachments. Thunderbird has a nice feature to display text attachments inline, so there is no need
to download it and open it with an external editor, or whatever.
And, I never get `git send-mail` work on my machine:
```
Send this email? ([y]es|[n]o|[e]dit|[q]uit|[a]ll): y
Unable to initialize SMTP properly. Check config and use --smtp-debug. VA
LUES: server=smtp.126.com encryption=tls hello=localhost.localdomain port
=465 at /usr/lib/git-core/git-send-email line 1684, <FIN> line 3.
```
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-10-04 13:46 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 18:34 LIU Hao
2022-10-01 20:02 ` Bernhard Reutner-Fischer
2022-10-02 12:54 ` LIU Hao
2022-10-03 5:03 ` Bernhard Reutner-Fischer
2022-10-04 8:06 ` LIU Hao
2022-10-04 19:45 ` Bernhard Reutner-Fischer
2022-10-04 12:44 ` LIU Hao
2022-10-04 13:13 ` Xi Ruoyao
2022-10-04 13:45 ` LIU Hao [this message]
2022-10-05 1:23 ` Xi Ruoyao
2022-10-10 15:56 ` LIU Hao
2022-10-11 13:22 ` LIU Hao
2022-10-14 9:39 ` Jonathan Yong
2022-10-19 13:55 ` Jonathan Yong
2022-10-19 19:53 ` Bernhard Reutner-Fischer
2022-10-20 1:25 ` LIU Hao
2022-10-21 9:58 ` Jonathan Wakely
2022-10-21 10:09 ` i.nixman
2022-10-21 10:48 ` Jonathan Wakely
2022-10-21 10:55 ` i.nixman
2022-10-21 11:36 ` LIU Hao
2022-10-21 11:54 ` i.nixman
2022-10-21 12:19 ` LIU Hao
2022-10-21 12:34 ` i.nixman
2022-10-24 3:40 ` LIU Hao
2022-10-24 20:50 ` Jacek Caban
2022-10-21 12:13 ` Jacek Caban
2022-10-21 12:29 ` LIU Hao
2022-10-21 12:40 ` Jacek Caban
2022-10-21 11:44 ` Eric Botcazou
2022-10-21 11:55 ` i.nixman
2022-10-21 12:30 ` Jacek Caban
2022-10-23 0:36 ` NightStrike
2022-10-24 6:53 ` i.nixman
2022-10-24 8:15 ` Eric Botcazou
2022-10-24 8:20 ` i.nixman
2022-10-31 9:18 ` Eric Botcazou
2022-10-31 15:22 ` i.nixman
2022-12-18 11:14 ` Jonathan Yong
2022-11-01 5:22 ` i.nixman
2022-11-01 9:09 ` Eric Botcazou
2022-11-02 12:05 ` i.nixman
2022-11-02 21:27 ` Eric Botcazou
2022-11-02 21:40 ` i.nixman
2022-12-16 17:18 ` Jonathan Wakely
2022-12-16 19:20 ` Eric Botcazou
2022-12-22 12:21 ` Jonathan Yong
2022-12-22 12:28 ` i.nixman
2022-12-23 23:59 ` Jonathan Yong
2022-12-24 5:58 ` NightStrike
2022-12-24 6:27 ` i.nixman
2022-12-24 13:50 ` i.nixman
2022-12-24 15:42 ` i.nixman
2022-12-24 15:57 ` i.nixman
2022-12-24 21:22 ` i.nixman
2022-12-25 1:10 ` Jonathan Yong
2023-01-09 21:56 ` Eric Botcazou
2022-12-24 6:22 ` i.nixman
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=a23ad853-2cc7-63af-99e6-362ade66fcd8@126.com \
--to=lh_mouse@126.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=xry111@xry111.site \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).