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 14:46:10 +0200 [thread overview]
Message-ID: <871rloke0d.fsf@gnu.org> (raw)
In-Reply-To: <86y2nxro6j.fsf@gmail.com> (zimoun's message of "Mon, 06 Jul 2020 11:24:36 +0200")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
> On Mon, 06 Jul 2020 at 10:37, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> I put the “Invoking” node under “Development”, not sure if that’s
>> the best place. Also, I considered doing a ‘guix git’ command,
>> of which ‘authenticate’ would be one sub-command and maybe ‘clone’
>> another one. But for ‘clone’ I thought that ‘guix download’ would
>> be a better fit. So I concluded that ‘guix git-authenticate’ was
>> a good choice in the end.
>
> On the topic of other subcommands, I have in mind log and tag.
>
> Currently, I have
>
> export CKT=~/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq
> export SRC=~/src/guix
>
> and I run "git -C $CKT" or "git -C $SRC", for example:
>
> 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’s not entirely clear to me what a ‘guix git log’ command would do in
fact: show the log for the ‘guix’ channel? For all channels (how?)?
For the specified channel? For what commit range?
> And the same for tagging commits. Which implies also improve what "guix
> pull" and "guix time-machine" accept.
Tagging commits is tricky because users only have a *cached* checkout.
So if we want persistent tags, we’ll have to develop a separate
mechanism. Could be useful, though perhaps redundant with the
(unimplemented) idea of tagging generation?
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.
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-07-06 12:47 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 [this message]
2020-07-06 13:27 ` zimoun
2020-07-06 19:48 ` Ludovic Courtès
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=871rloke0d.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).