From: ludo@gnu.org (Ludovic Courtès)
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Display diffs between generations.
Date: Thu, 20 Oct 2016 14:36:52 +0200 [thread overview]
Message-ID: <87funrci3f.fsf@gnu.org> (raw)
In-Reply-To: <87vawo57sn.fsf@gnu.org> (Roel Janssen's message of "Wed, 19 Oct 2016 23:48:56 +0200")
Roel Janssen <roel@gnu.org> skribis:
> Ludovic Courtès writes:
[...]
>> I don’t think so. The old behavior will always be available by
>> specifying a single generation anyway:
>>
>> guix package --list-generations=42
>>
>> It may be worth mentioning this in the manual.
>>
>> My understanding of the discussion referred above is that people were
>> fine with that (or indifferent ;-)).
>
> Then the following patch should be it. I applied your genius
> suggestions of using @code{display-entry} instead of
> @code{display-entries}. I learned something new again today. :-)
Heh. :-)
>From 5630a512f16c6677fd5b0b8085e2ef15cb10499b Mon Sep 17 00:00:00 2001
> From: Roel Janssen <roel@gnu.org>
> Date: Wed, 19 Oct 2016 23:38:11 +0200
> Subject: [PATCH] guix package: Display generation diffs.
>
> * guix/ui.scm (display-profile-content-diff): New variable.
> * guix/scripts/package.scm (process-query): Use display-profile-content-diff.
The code LGTM, but it doesn’t implement the behavior I suggested above
for --list-generations=42, which I think I didn’t explain correctly.
I think what I’m suggesting is that the first matching generation should
be displayed in full using ‘display-profile-content’, and subsequent
generations would be displayed as a diff.
Thus, when viewing a single generation, as with --list-generations=42,
we’d only display the full contents of that generation.
Does that make sense?
Sorry for not clarifying this in the first place! I guess that wasn’t
entirely clear to me either. ;-)
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-10-20 12:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 23:02 Display diffs between generations Roel Janssen
2016-08-29 16:25 ` Ludovic Courtès
2016-08-29 19:08 ` Roel Janssen
2016-08-31 20:52 ` Ludovic Courtès
2016-08-31 21:11 ` Vincent Legoll
2016-09-01 12:12 ` Ludovic Courtès
2016-09-03 13:03 ` Vincent Legoll
2016-09-04 16:53 ` Roel Janssen
2016-10-10 20:30 ` Ludovic Courtès
2016-10-11 7:19 ` Roel Janssen
2016-10-18 12:43 ` Roel Janssen
2016-10-19 20:22 ` Ludovic Courtès
2016-10-19 21:48 ` Roel Janssen
2016-10-20 12:36 ` Ludovic Courtès [this message]
2016-10-20 12:56 ` Roel Janssen
2016-10-20 19:38 ` Ludovic Courtès
2016-10-21 9:37 ` Roel Janssen
2016-10-21 14:40 ` Benz Schenk
2016-10-24 20:33 ` Ludovic Courtès
2016-10-25 16:01 ` Roel Janssen
2016-10-26 11:13 ` Benz Schenk
2016-10-26 11:38 ` Ludovic Courtès
2016-10-26 12:58 ` Roel Janssen
2016-09-04 22:12 ` Ludovic Courtès
2016-09-05 7:52 ` Hartmut Goebel
2016-09-05 10:38 ` Vincent Legoll
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=87funrci3f.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=roel@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).