From: Jelle Licht <jlicht@fsfe.org>
To: "Ludovic Courtès" <ludo@gnu.org>, "Guix Devel" <guix-devel@gnu.org>
Subject: Re: Flag day for simplified package inputs
Date: Fri, 19 Nov 2021 16:29:54 +0100 [thread overview]
Message-ID: <86o86gjh8t.fsf@fsfe.org> (raw)
In-Reply-To: <87k0h4i3io.fsf@gnu.org>
Hey Guix,
Ludovic Courtès <ludo@gnu.org> writes:
> Hello Guix!
>
> As a reminder, the plan I proposed¹ is to have a “flag day” shortly
> before ‘core-updates-frozen’ is merged into ‘master’ when we would run
> ‘guix style’ on the whole repo, thereby removing input labels from most
> packages.
<snip>
> If everything goes well, this could happen in a few days.
>
> Thoughts?
Slightly OT, but I think we should think about it now rather than after
the merge.
As with any bulk change, this change will clobber git blame for the
forseeable future for a big chunk of the code.
When applying this and future bulk changes, could we perhaps list the
specific commits (+ commented shortlog line) in a file. To clarify, if
we were to store these commits in `.git-blame-ignore-revs', later on we
can instruct users to run:
--8<---------------cut here---------------start------------->8---
git config blame.ignoreRevsFile .git-blame-ignore-revs
--8<---------------cut here---------------end--------------->8---
to ignore the bulk change for git blame purposes.
It seems like a maintainable way to mitigate some of the (IMO) major
disadvantages that we bring in by applying bulk changes.
NB, we could still ponder and discuss this approach at a later point in
time, but perhaps we want to deal with some of these issues in a
different way that cannot be delayed as easily.
WDYT?
- Jelle
next prev parent reply other threads:[~2021-11-19 15:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 15:11 Flag day for simplified package inputs Ludovic Courtès
2021-11-19 15:29 ` Jelle Licht [this message]
2021-11-22 13:22 ` Ludovic Courtès
2021-11-22 15:13 ` Jelle Licht
2021-11-23 17:08 ` Ludovic Courtès
2021-11-29 11:49 ` Jelle Licht
2021-12-01 17:50 ` Ludovic Courtès
2021-12-13 15:17 ` Jelle Licht
2021-12-20 17:52 ` Ludovic Courtès
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=86o86gjh8t.fsf@fsfe.org \
--to=jlicht@fsfe.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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).