unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: Konrad Hinsen <konrad.hinsen@fastmail.net>,
	63726@debbugs.gnu.org, Simon Tournier <zimon.toutoune@gmail.com>
Subject: bug#63726: time-machine without options does not get the latest commit
Date: Thu, 17 Aug 2023 10:39:55 -0400	[thread overview]
Message-ID: <87sf8hg2bo.fsf@gmail.com> (raw)
In-Reply-To: <874jkxyd7d.fsf@inria.fr> ("Ludovic Courtès"'s message of "Thu, 17 Aug 2023 16:07:34 +0200")

Hi Ludovic,

Ludovic Courtès <ludovic.courtes@inria.fr> writes:

> Hi,
>
> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>
>> Ludovic Courtès <ludovic.courtes@inria.fr> writes:
>>
>>> Hey!
>>>
>>> Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
>>>
>>>> This looks good to me. In practice, I doubt anyone would use -q with
>>>> time-machine, because it makes more sense to specify an explicit channel
>>>> file every time.
>>>
>>> Yeah.  The use case I have in mind is something like:
>>>
>>>   guix time-machine -q --commit=XYZ -- build hello
>>>
>>> Useful, for example, to share a way to reproduce a bug, making sure
>>> there’s nothing but the ‘guix’ channel.
>>
>> The '-q' short option by itself is a bit opaque / hard to memorize;
>> perhaps complementing it with a self explanatory
>> '--ignore-channel-files' long option name would be a good idea?
>
> Yes, I did that in v2, as Simon suggested.

Oh, I had missed that.  Thank you!

> (‘-q’ seems to be a relatively common convention: emacs, guile, and also
> ‘guix repl’.)

I think it's also commonly used as '--quiet', in other circles :-).

-- 
Thanks,
Maxim




  reply	other threads:[~2023-08-17 14:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25 13:52 bug#63726: time-machine without options does not get the latest commit Simon Tournier
2023-05-25 21:03 ` Ludovic Courtès
2023-05-26  9:31   ` Simon Tournier
2023-05-26 11:15   ` Konrad Hinsen
2023-05-30 13:32     ` Simon Tournier
2023-06-01 15:01       ` Konrad Hinsen
2023-08-11 15:36         ` Ludovic Courtès
2023-08-14 10:13           ` Konrad Hinsen
2023-08-16 13:51             ` Simon Tournier
2023-08-17  8:42             ` Ludovic Courtès
2023-08-17 13:41               ` Maxim Cournoyer
2023-08-17 14:07                 ` Ludovic Courtès
2023-08-17 14:39                   ` Maxim Cournoyer [this message]
2023-09-04 16:55   ` Simon Tournier
2023-09-08 15:39     ` Ludovic Courtès

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=87sf8hg2bo.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=63726@debbugs.gnu.org \
    --cc=konrad.hinsen@fastmail.net \
    --cc=ludovic.courtes@inria.fr \
    --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).