From: ludo@gnu.org (Ludovic Courtès)
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Display diffs between generations.
Date: Mon, 29 Aug 2016 18:25:29 +0200 [thread overview]
Message-ID: <87d1kry22u.fsf@gnu.org> (raw)
In-Reply-To: <87eg59izmw.fsf@gnu.org> (Roel Janssen's message of "Sun, 28 Aug 2016 01:02:47 +0200")
Hi Roel,
I’ve just tried the patch and I think it’s awesome! I’ve also always
been dissatisfied with what ‘--list-generations’ provides—it’s
inconvenient as soon as you have more than a handful packages.
Perhaps we could add an optional argument to --list-generations where:
--list-generations
would be equivalent to:
--list-generations=diff
and:
--list-generations=full
would restore the previous behavior. It doesn’t cost much to do that.
WDYT?
I have only minor stylistic comments:
Roel Janssen <roel@gnu.org> skribis:
> +(define (display-profile-content-diff profile number)
Or just ‘display-profile-diff’?
> + "Display the changed packages in PROFILE with generation specified by NUMBER."
“… compared to generation NUMBER”?
> + (define (equal-entry? first second)
> + (string= (manifest-entry-item first)
> + (manifest-entry-item second)))
> +
> + (define* (display-entries entries #:optional (prefix " "))
> + (for-each
> + (match-lambda
> + (($ <manifest-entry> name version output location _)
> + (format #t " ~a ~a\t~a\t~a\t~a~%"
> + prefix name version output location)))
> + entries))
In general, I find it clearer to define the singular form and inline the
‘for-each’:
(define display-entry
(match-lambda …))
…
(for-each display-entry entries)
Otherwise LGTM!
Thank you for addressing this!
Ludo’.
next prev parent reply other threads:[~2016-08-29 16:25 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1kry22u.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 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.