From: "Ludovic Courtès" <ludo@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
Cc: 54000@debbugs.gnu.org
Subject: [bug#54000] [PATCH 0/2] Not showing upgraded/added packages in 'guix pull'
Date: Thu, 17 Feb 2022 11:19:02 +0100 [thread overview]
Message-ID: <87fsohpzhl.fsf@gnu.org> (raw)
In-Reply-To: <13cb5b9b650f86917e44db255f2ad92d679d3226.camel@ist.tugraz.at> (Liliana Marie Prikler's message of "Tue, 15 Feb 2022 14:55:29 +0100")
Hi,
Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> skribis:
> Am Montag, dem 14.02.2022 um 17:38 +0100 schrieb Ludovic Courtès:
>> Hello!
>>
>> As a followup to <https://issues.guix.gnu.org/53909>, these patches
>> remove the list of added/upgraded packages from the output of
>> ‘guix pull’ (upon completion) and ‘guix pull --news’.
[...]
>> pull: '--news' no longer shows package lists.
>> pull: No longer print upgraded/added packages upon completion.
> What if I wanted that information however?
Is it an actual use case or speculation?
> Does `guix pull --news -- details` still give it to me?
Not with this patch, but we could do that *if* there’s a need.
> I don't really want to do `guix pull -l 1d --details` instead.
OK. So far, my impression was that this information was hardly used at
all, which is why it seemed reasonable to keep it behind ‘--details
--list-generations’.
I’m open to supporting ‘--news --details’, but only if it corresponds to
a real use case.
Thanks,
Ludo’.
next prev parent reply other threads:[~2022-02-17 10:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 16:38 [bug#54000] [PATCH 0/2] Not showing upgraded/added packages in 'guix pull' Ludovic Courtès
2022-02-14 16:41 ` [bug#54000] [PATCH 1/2] pull: '--news' no longer shows package lists Ludovic Courtès
2022-02-14 16:41 ` [bug#54000] [PATCH 2/2] pull: No longer print upgraded/added packages upon completion Ludovic Courtès
2022-02-15 13:55 ` [bug#54000] [PATCH 0/2] Not showing upgraded/added packages in 'guix pull' Liliana Marie Prikler
2022-02-17 10:19 ` Ludovic Courtès [this message]
2022-02-17 10:30 ` Liliana Marie Prikler
2022-02-17 12:04 ` zimoun
2022-02-17 12:52 ` Liliana Marie Prikler
2022-02-17 14:41 ` zimoun
2022-02-18 9:08 ` Ludovic Courtès
2022-02-18 9:20 ` Liliana Marie Prikler
2022-02-27 22:15 ` bug#54000: " 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=87fsohpzhl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=54000@debbugs.gnu.org \
--cc=liliana.prikler@ist.tugraz.at \
/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).