unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: [Outreachy] Feedback on 'guix git log' subcommand
Date: Mon, 01 Feb 2021 16:18:34 +0100	[thread overview]
Message-ID: <871rdzn7ed.fsf@gnu.org> (raw)
In-Reply-To: <86im7ghd9c.fsf@gmail.com> (zimoun's message of "Fri, 29 Jan 2021 00:07:11 +0100")

Hi,

zimoun <zimon.toutoune@gmail.com> skribis:

> On Thu, 28 Jan 2021 at 00:53, Magali <magalilemes00@gmail.com> wrote:
>
>> On a side note, I've been blogging about it at
>> <https://magalilemes.gitlab.io/blog>.
>
> Nice readings! :-)

Seconded!

>> Below are a few examples of the options currently available:
>>
>> ./pre-inst-env guix git log --format=medium
>> ./pre-inst-env guix git log --oneline
>> ./pre-inst-env guix git log --channel-cache-path
>> ./pre-inst-env guix git log --channel-cache-path=guix
>
> Cool!
>
> An example, the recent update of setuptools breaks python2-setuptools.
>
> $ ./pre-inst-env guix git log --oneline \
>>   | grep 'python-setuptools:' | grep Update
> b3ca2b4 gnu: python-setuptools: Update to 40.8.0.
> d0205df gnu: python-setuptools: Update to 40.0.0.
> 62a9a23 gnu: python-setuptools: Update to 18.3.1.
> d3d656c gnu: python-setuptools: Update to 12.1.
> d660f7b gnu: python-setuptools: Update to 31.0.0.
> e39d493 gnu: python-setuptools: Update to 41.0.1.
> 3142dac gnu: python-setuptools: Update to 52.0.0.
>
>
> Ah, the order seems weird, “git log” says:
>
> 3142daccbe gnu: python-setuptools: Update to 52.0.0.
> e39d4933d1 gnu: python-setuptools: Update to 41.0.1.
> b3ca2b45d1 gnu: python-setuptools: Update to 40.8.0.
> d0205dfd92 gnu: python-setuptools: Update to 40.0.0.
> d660f7be6d gnu: python-setuptools: Update to 31.0.0.
> 62a9a23bf9 gnu: python-setuptools: Update to 18.3.1.
> d3d656c5fb gnu: python-setuptools: Update to 12.1.

It might be breadth-first vs. depth-first?  I remember having
difficulties finding out which ordering ‘git log’ chooses when I was
working on ‘guix pull --news’.

At any rate, this all looks promising.  Thanks for keeping us posted,
Magali!

Ludo’.


  parent reply	other threads:[~2021-02-01 15:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28  3:53 [Outreachy] Feedback on 'guix git log' subcommand Magali
2021-01-28 23:07 ` zimoun
2021-01-30  1:30   ` Magali
2021-02-01  7:27     ` zimoun
2021-02-01 15:18   ` Ludovic Courtès [this message]
2021-01-29  0:04 ` [Outreachy] 'guix git log' slowness? 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=871rdzn7ed.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@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).