From: jgart via Guix-patches via <guix-patches@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 53865-done@debbugs.gnu.org, 53865@debbugs.gnu.org
Subject: [bug#53865] [PATCH] gnu: ruby-parser: Update to 3.1.0.0.
Date: Wed, 9 Feb 2022 17:10:11 -0500 [thread overview]
Message-ID: <20220209171011.GB4308@gac.attlocal.net> (raw)
In-Reply-To: <87k0e3vimj.fsf@nicolasgoaziou.fr>
On Wed, 09 Feb 2022 22:24:04 +0100 Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> jgart via Guix-patches via <guix-patches@gnu.org> writes:
>
> > What do you think if we were to add a smart user message to the `guix refresh
> > --list-dependent ...` command?
> >
> > I was thinking something along these lines:
> >
> > ```
> > $ guix refresh --list-dependent ruby-parser
> >
> > Building the following 1991 packages would ensure 5378 dependent packages are rebuilt: ...
> >
> > ruby-parser reported 5000+ packages. According to Submitting Patches section of
> > the manual, above 1800, it should go to core-updates (at the moment).
> > ```
> >
> > Like that, the command reminds the user/calculates for the user what
> > branch to put the package in.
> >
> > I'm imagining it would be as easy as just getting the length of the output and
> > matching against it the appropriate message?
>
> This would only be useful for people wanting to submit a patch who have
> forgotten about that rule. For everyone else, this is just technical
> noise. I don't think this is something terribly useful.
>
> In any case, you can create another bug report to suggest it as an UI
> improvement.
If you think it's bloat, I can get behind that.
I should just memorize the rule already ;()
I was thinking it could be useful for newcomers to Guix but maybe they
should just find it in the manual.
I know I missed that part in the manual when I was more of a fresher
and I still do sometimes as this patch attested.
prev parent reply other threads:[~2022-02-09 22:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 2:08 [bug#53865] [PATCH] gnu: ruby-parser: Update to 3.1.0.0 jgart via Guix-patches via
2022-02-09 15:05 ` bug#53865: " Nicolas Goaziou
2022-02-09 18:02 ` [bug#53865] " jgart via Guix-patches via
2022-02-09 20:00 ` Nicolas Goaziou
2022-02-09 21:05 ` jgart via Guix-patches via
2022-02-09 21:16 ` jgart via Guix-patches via
2022-02-09 21:24 ` Nicolas Goaziou
2022-02-09 22:10 ` jgart via Guix-patches via [this message]
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=20220209171011.GB4308@gac.attlocal.net \
--to=guix-patches@gnu.org \
--cc=53865-done@debbugs.gnu.org \
--cc=53865@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=mail@nicolasgoaziou.fr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.