From: Eli Schwartz <eschwartz93@gmail.com>
To: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: [RFC PATCH 1/1] nix: add a simple flake nix shell
Date: Wed, 31 Jan 2024 17:19:16 -0500 [thread overview]
Message-ID: <9d98e9f5-3710-4941-a9ee-b0ca5fbb4223@gmail.com> (raw)
In-Reply-To: <20240131214520.142408-1-vincenzopalazzodev@gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1762 bytes --]
On 1/31/24 4:43 PM, Vincenzo Palazzo wrote:
> This commit is specifically targeting enhancements in
> Nix support for GCC development. This initiative stems
> from the recognized need within our community for a more
> streamlined and efficient development process when using Nix.
>
> Please not that in this case the Nix tool is used to define
> what should be in the dev environment, and not as a NixOS distro
> package manager.
>
> Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
> ---
I was originally trying to figure out what the idea behind this patch
was, as I recalled discussing the patch before. Then I double checked
the mailing list and saw:
https://inbox.sourceware.org/gcc-patches/20240131214259.142253-1-vincenzopalazzodev@gmail.com/T/#u
One thing that can potentially reduce confusion here is:
- use git send-email -v2 to mark the patch as an update to an existing
patch.
- Use the --annotate option, and edit the patch before sending it. Right
here, after the "---" and in the same semantic patch section as the
diffstat, you can put arbitrary non-patch commentary. It is
essentially comments for patches -- it won't be included in the commit
message when the patch is applied with `git am`. It is common to
insert something that looks like this:
v2: moved the flake to contrib/ instead of installing it at the root of
the repository
> .gitignore | 1 +
> contrib/nix/flake.nix | 35 +++++++++++++++++++++++++++++++++++
> 2 files changed, 36 insertions(+)
> create mode 100644 contrib/nix/flake.nix
>
> diff --git a/.gitignore b/.gitignore
> index 93a16b0b950..801b1d1709e 100644
> --- a/.gitignore
> +++ b/.gitignore
--
Eli Schwartz
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 18399 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-01-31 22:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 21:43 Vincenzo Palazzo
2024-01-31 22:19 ` Eli Schwartz [this message]
2024-02-01 21:04 ` Vincenzo Palazzo
-- strict thread matches above, loose matches on Subject: below --
2023-12-05 0:55 Vincenzo Palazzo
2023-12-05 1:02 ` Andrew Pinski
2023-12-05 1:07 ` Jeff Law
2023-12-05 1:38 ` Vincenzo Palazzo
2023-12-05 1:54 ` Jeff Law
2023-12-05 2:01 ` Vincenzo Palazzo
2023-12-05 2:02 ` Vincenzo Palazzo
2023-12-05 4:25 ` Eli Schwartz
2023-12-05 8:59 ` Richard Biener
2023-12-05 10:35 ` Vincenzo Palazzo
2023-12-05 12:43 ` Eli Schwartz
2023-12-11 16:10 ` Vincenzo Palazzo
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=9d98e9f5-3710-4941-a9ee-b0ca5fbb4223@gmail.com \
--to=eschwartz93@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=vincenzopalazzodev@gmail.com \
/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).