From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 42225@debbugs.gnu.org
Subject: [bug#42225] [PATCH 0/5] Add 'guix git-authenticate' command
Date: Mon, 06 Jul 2020 21:48:56 +0200 [thread overview]
Message-ID: <87fta4ifvb.fsf@gnu.org> (raw)
In-Reply-To: <CAJ3okZ1PXeG96Ws+1azxi_K96+n2XsOtaxecRwhYt4igrg9cXQ@mail.gmail.com> (zimoun's message of "Mon, 6 Jul 2020 15:27:26 +0200")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
> On Mon, 6 Jul 2020 at 14:46, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> > git -C $SRC log | grep Update
>> >
>> > And I would like to be able to simply run;
>> >
>> > guix git log | grep Update
>>
>> Good point. Though hopefully this particular use case (finding new
>> package updates) is well served by ‘guix pull --news’, no?
>
> It is not for new package updates, but the contrary. :-)
> I use it for searching versions back in time. Which commit introduces
> which version.
>
> To be honest, I am almost never use "guix pull --news" because I am
> pulling once every full moon, and even when I do, I run an ugly script
> like:
>
> #!/bin/bash
>
> # url-cache-directory from guix/git.scm
> # pjmkgl... = hash("https://git.savannah.gnu.org/git/guix.git")
> CACHE=~/.cache/guix/checkouts
> CHECKOUT=${CACHE}/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq
>
> printf "Updating local checkout:\n'$CHECKOUT'..."
> git -C $CHECKOUT pull -q
> echo " done."
>
> guix pull --commit=$(git -C $CHECKOUT \
> log \
> --before=$(date --date='2 weeks ago' +%Y-%m-%d) \
> --format="%h" | head -n1) \
> $@
>
> because I do want the substitutes available. Well, for example, I
> run: "guix pull --news" and I get 15 new packages and 367 packages
> upgraded.
We’re drifting off-topic, but this is interesting. I just hope few
people do that, but at least it’s a reminder of the sad situation
wrt. substitute availability.
I don’t understand why you wouldn’t run ‘guix pull --news’ though. It
provides useful info beyond packages, doesn’t it?
[...]
>> In the short term, we don’t need to solve all these problems: we can
>> also go for ‘git-authenticate’ and rename it once we have these other
>> commands.
>
> I have learnt that renaming will not work. :-)
> Because backward compatibilities and break the workflow of someone.
> So I would take the other route, go for "guix git authenticate" and
> hoping that other commands would come soon.
Well, this particular renaming would be easy: it’s really just renaming,
with a known name, a situation very different from that of ‘guix
environment’ if that’s what you were alluding to.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-07-06 19:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 8:37 [bug#42225] [PATCH 0/5] Add 'guix git-authenticate' command Ludovic Courtès
2020-07-06 8:43 ` [bug#42225] [PATCH 1/5] git-authenticate: Factorize 'authenticate-repository' Ludovic Courtès
2020-07-06 8:43 ` [bug#42225] [PATCH 2/5] Add 'etc/historical-authorizations' Ludovic Courtès
2020-07-06 8:43 ` [bug#42225] [PATCH 3/5] git: Add 'with-git-error-handling' Ludovic Courtès
2020-07-06 8:43 ` [bug#42225] [PATCH 4/5] Add 'guix git-authenticate' Ludovic Courtès
2020-07-06 8:43 ` [bug#42225] [PATCH 5/5] maint: Remove 'build-aux/git-authenticate.scm' Ludovic Courtès
2020-07-06 9:24 ` [bug#42225] [PATCH 0/5] Add 'guix git-authenticate' command zimoun
2020-07-06 12:46 ` Ludovic Courtès
2020-07-06 13:27 ` zimoun
2020-07-06 19:48 ` Ludovic Courtès [this message]
2020-07-06 21:27 ` zimoun
2020-07-11 11:01 ` bug#42225: " Ludovic Courtès
2020-07-16 0:12 ` [bug#42225] " zimoun
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=87fta4ifvb.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=42225@debbugs.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 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).