From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: "Ludovic Courtès" <ludo@gnu.org>, zimoun <zimon.toutoune@gmail.com>
Cc: 54000@debbugs.gnu.org
Subject: [bug#54000] [PATCH 0/2] Not showing upgraded/added packages in 'guix pull'
Date: Fri, 18 Feb 2022 10:20:36 +0100 [thread overview]
Message-ID: <3456b0651ed89758801b8b68071859f0023b5638.camel@ist.tugraz.at> (raw)
In-Reply-To: <87k0dslexx.fsf@gnu.org>
Am Freitag, dem 18.02.2022 um 10:08 +0100 schrieb Ludovic Courtès:
> Hey comrades, hold your horses! :-)
>
> Since there’s a need for this, we can make ‘--details’ print package
> lists when combined with ‘--news’; it doesn’t cost us anything,
> that’s OK.
Regarding the issue simon raised w.r.t. --details implying -l, I think
--details should only imply listing the latest generation if -l is not
specified. That way --news --details would (hopefully) work as I
intended, and specifying one without the other would only print that
part.
On a separate note, would/should guix describe be affected by this?
Its output appear currently the same as `guix pull -l
$CURRENT_GENERATION', but I haven't tested this on a generation
including news. My guess would be "no" as guix describe currently
doesn't accept --news.
Cheers
next prev parent reply other threads:[~2022-02-18 9:21 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3456b0651ed89758801b8b68071859f0023b5638.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=54000@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=zimon.toutoune@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.
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.