From: Magali <magalilemes00@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>,
"Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>, Mathieu Othacehe <othacehe@gnu.org>
Subject: Re: [outreachy] Walk through the Git history (guix git {authenticate,log})
Date: Fri, 11 Dec 2020 16:01:56 -0300 [thread overview]
Message-ID: <e13b1718-aa97-1c9f-8792-b6f3503bcb6a@gmail.com> (raw)
In-Reply-To: <86r1nwfdeu.fsf@gmail.com>
Hi,
On 11/12/2020 14:41, zimoun wrote:
> Hi,
>
> Discussing how to walk through the Git history
> ~/.cache/guix/checkouts/<hash>, there is 2 ways to do:
>
> 1. Loop with commit-parents as it is done for ’commit-closure’ in
> guix/git.scm.
>
> 2. Bind git_revwalk_* and use it instead.
>
> WDYT?
>
> Well, #1 is more straightforward but less efficient, IIUC.
>
>
> All the best,
> simon
I think #2 is the way to go. It may be more difficult to implement right
now, but in the future it'll make things easier if we think about adding
an option that allows us to choose the order the commits will be shown,
for instance.
Magali
next prev parent reply other threads:[~2020-12-11 19:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 17:41 [outreachy] Walk through the Git history (guix git {authenticate, log}) zimoun
2020-12-11 19:01 ` Magali [this message]
2020-12-12 12:24 ` [outreachy] Walk through the Git history (guix git {authenticate,log}) zimoun
2020-12-12 17:24 ` Magali
2020-12-12 17:49 ` [outreachy] Walk through the Git history zimoun
2020-12-14 10:20 ` Ludovic Courtès
2020-12-15 15:20 ` [outreachy] Walk through the Git history (guix git {authenticate,log}) Magali
2020-12-16 9:35 ` zimoun
2020-12-18 15:34 ` Ludovic Courtès
2020-12-19 3:18 ` Magali
2020-12-12 8:42 ` Mathieu Othacehe
2020-12-12 12:10 ` 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=e13b1718-aa97-1c9f-8792-b6f3503bcb6a@gmail.com \
--to=magalilemes00@gmail.com \
--cc=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=othacehe@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).