From: Mark H Weaver <mhw@netris.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 57788@debbugs.gnu.org
Subject: [bug#57788] [PATCH] gnu: rust: Disable debug info to reduce build requirements
Date: Fri, 28 Oct 2022 06:40:27 -0400 [thread overview]
Message-ID: <87wn8kfcy1.fsf@netris.org> (raw)
In-Reply-To: <Y0aa1J2+y+QVGX6D@3900XT>
Hi Efraim,
I was surprised to see commit 01be1973f464cb81cdece54f7858f0dee46abb50
attributed solely to me, although I did not actually author that commit.
In the future, please do not attribute commits to me that I did not
write or approve of. At minimum, if you modify a commit that I
proposed, please add a "Modified-by" line in the commit log. If you
made radical changes to a commit that I proposed, better to list
yourself as author and maybe say "based on a proposal by Mark H Weaver"
in the commit log.
One important modification that got lost in your simplified commit was
the change I made to mrustc/tools/minicargo/build.cpp, which I evidently
found necessary. Without that change, I do not know if Rust can still
be bootstrapped on a small machine such as mine.
Anyway, thanks for working on it, and for the other important work
you've done on dramatically shortening the Rust bootstrap.
Regards,
Mark
--
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>.
next prev parent reply other threads:[~2022-10-28 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 23:56 [bug#57788] [PATCH] gnu: rust: Disable debug info to reduce build requirements Mark H Weaver
2022-10-07 10:36 ` Efraim Flashner
2022-10-07 22:04 ` Mark H Weaver
2022-10-12 10:45 ` Efraim Flashner
2022-10-28 10:40 ` Mark H Weaver [this message]
2022-10-29 19:39 ` Efraim Flashner
2022-11-01 5:11 ` Mark H Weaver
2022-11-01 5:13 ` bug#57788: " Mark H Weaver
2022-10-09 12:38 ` [bug#57788] " Efraim Flashner
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wn8kfcy1.fsf@netris.org \
--to=mhw@netris.org \
--cc=57788@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).