all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Magali <magalilemes00@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>,
	zimoun <zimon.toutoune@gmail.com>,
	"Guix Devel" <guix-devel@gnu.org>
Subject: [Outreachy] Strategy to implement guix git log --pretty=<string>
Date: Wed, 6 Jan 2021 01:35:26 -0300	[thread overview]
Message-ID: <c2de6cf1-b8af-5008-ebbd-d1c587ce1064@gmail.com> (raw)

Hello Guix,

As you might know, as part of my Outreachy internship I'm currently
working on implementing the subcommand 'guix git log', for browsing the
history of all packages. So far, it works with '--oneline' and
'--format=<FORMAT>', and FORMAT can be 'oneline', 'medium' or 'full'. If
you want to see it, the code can be found at
https://gitlab.com/magalilemes/guix

On the road to adding another option to the subcommand,
'--pretty=<string>' arose as an idea. With git log, you can do something
like
git log pretty=<string>
And this string can have placeholders, such as %h for showing the short
hash of a commit, and %s for showing the commit subject. For instance,
you could have git log --pretty="%h %s" and this would display the
commit history log with the short hash and subject of commits.

So, in order to implement 'guix git log --pretty=<string>', I'd like
help with a strategy to parse the string. Any examples, ideas and tips
would be really appreciated.

Cheers,

Magali




             reply	other threads:[~2021-01-06  4:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-06  4:35 Magali [this message]
2021-01-06  8:03 ` [Outreachy] Strategy to implement guix git log --pretty=<string> Gábor Boskovits
2021-01-14 21:29 ` Ludovic Courtès
2021-01-18 15:02   ` zimoun
  -- strict thread matches above, loose matches on Subject: below --
2021-01-06  8:10 Leo Prikler
2021-01-18 14:45 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c2de6cf1-b8af-5008-ebbd-d1c587ce1064@gmail.com \
    --to=magalilemes00@gmail.com \
    --cc=boskovits@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.