unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: wishlist: Guix tagging/logging
Date: Wed, 4 Mar 2020 17:23:53 +0100	[thread overview]
Message-ID: <CAJ3okZ2bAH5PSx8RnuqHvXOp=XWyW4O0zmxmBJ=Tb6ySd7jt9A@mail.gmail.com> (raw)
In-Reply-To: <87sgioyv54.fsf@ambrevar.xyz>

On Wed, 4 Mar 2020 at 16:52, Pierre Neidhardt <mail@ambrevar.xyz> wrote:

> So we could do as you said, but then we need a way to propagate the tags
> across all checkouts in .cache/guix/checkouts.

I do not know the (inferior) internals.
And currently I do not have the time to give a look into the sources
to crunch concrete details. :-)
So, it is hard for me to discuss further some "implementation
details". That's maybe why I pointed to your attention this wishlist.
;-)


> Otherwise, on the next guix pull  the tags would be lost.

Maybe not, if "guix pull" is simply an overlay to "git pull".
Well, I cannot tell because I do not know the internal details. With
*if* my aunt becomes my uncle. ;-)


My point is: since all or part of Git repo information is somehow
already locally there, then all or part of this information should
somehow be exposed at the Guix CLI level. The 2 first features missing
me are "git tag" and "git log".
However, I do not have more clue on how to process then. :-D
I mean right now I have more use-cases in mind than concrete
implementation details. :-)


Cheers,
simon

      reply	other threads:[~2020-03-04 16:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-28 11:18 wishlist: Guix tagging/logging zimoun
2020-02-11  8:47 ` Pierre Neidhardt
2020-03-03 22:56   ` zimoun
2020-03-04  8:16     ` Pierre Neidhardt
2020-03-04 14:32       ` zimoun
2020-03-04 15:52         ` Pierre Neidhardt
2020-03-04 16:23           ` zimoun [this message]

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='CAJ3okZ2bAH5PSx8RnuqHvXOp=XWyW4O0zmxmBJ=Tb6ySd7jt9A@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).