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: ...
Date: Sat, 12 Dec 2020 14:24:22 -0300 [thread overview]
Message-ID: <ccfa6c67-3e2e-0d9b-d8aa-05127fc95e31@gmail.com> (raw)
In-Reply-To: <86lfe3fc0t.fsf@gmail.com>
Hey,
On 12/12/2020 09:24, zimoun wrote:
> Awaiting how to walk the history tree, I am proposing to use the loop as
> Mathieu said. However, ’match’ is preferred over ’car’.
I got curious as to why it is preferred, hehe. Is there a special reason?
> Well, ’commit-list’ is far from perfect because all the log is traversed
> and the list reversed, aside that the first commit is not captured,
> etc. But I hope you get the idea. It is a starting point to implement a
> draft of:
>
> guix git log --oneline
Understood. I'll start working on it.
Magali
next prev parent reply other threads:[~2020-12-12 19:19 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 ` [outreachy] Walk through the Git history (guix git {authenticate,log}) Magali
2020-12-12 12:24 ` zimoun
2020-12-12 17:24 ` Magali [this message]
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=ccfa6c67-3e2e-0d9b-d8aa-05127fc95e31@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).