From: Tomas Volf <~@wolfsden.cz>
To: Remco van 't Veer <remco@remworks.net>
Cc: Efraim Flashner <efraim@flashner.co.il>, help-guix@gnu.org
Subject: Re: guix package -u . --dry-run equivalent for guix home
Date: Sun, 10 Dec 2023 01:20:32 +0100 [thread overview]
Message-ID: <ZXUEUPk9eF5yxiNs@ws> (raw)
In-Reply-To: <87a5qjtg51.fsf@remworks.net>
[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]
On 2023-12-09 18:55:22 +0100, Remco van 't Veer wrote:
>
> 2023/12/07, Tomas Volf:
>
> > [[PGP Signed Part:Undecided]]
> > On 2023-12-07 09:42:47 +0100, Remco van 't Veer wrote:
> >> How are people (with update junky tendencies like me) using guix-home?
> >> Run guix-home-reconfigure after every guix-pull?
> >
> > I in general just check the commit messages in the range that was pulled to see
> > if there is anything interesting. And reconfigure only in that case.
>
> Yeah, I have guix master from savannah in a RSS reader but miss a lot
> because it only returns the latest 10 commits. Do your have a local
> clone to get the logs from
Right so the thing is I do not run stock Guix, but a fork with some (very) light
modifications. So I need to merge updates from the Guix proper periodically.
And those merge commits are configured to provide in the commit message the very
information I need:
https://git.sr.ht/~graywolf/guix/commit/96ffe69d09c7abd4a80b632eb53c064e97e62141
> or is their some trick to get the logs from the commits guix-pull just
> fetched?
When `guix pull'-ing, it gives you a message like this:
Authenticating channel 'guix', commits 028e445 to 32c6a3a (9 new commits)...
So I would just use `git log --oneline 028e445..32c6a3a' in the Guix repository
(which I do have local clone anyway) to get the same list I have in the commit
message right now.
Hope this helps,
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-12-10 0:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 8:58 guix package -u . --dry-run equivalent for guix home Remco van 't Veer
2023-12-06 20:36 ` Efraim Flashner
2023-12-07 8:42 ` Remco van 't Veer
2023-12-07 10:05 ` Efraim Flashner
2023-12-09 17:48 ` Remco van 't Veer
2023-12-07 13:24 ` Tomas Volf
2023-12-09 17:55 ` Remco van 't Veer
2023-12-10 0:20 ` Tomas Volf [this message]
2023-12-10 8:13 ` Remco van 't Veer
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=ZXUEUPk9eF5yxiNs@ws \
--to=~@wolfsden.cz \
--cc=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=remco@remworks.net \
/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.
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).