git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Karthik Nayak <karthik.188@gmail.com>
To: Git <git@vger.kernel.org>
Cc: Christian Couder <christian.couder@gmail.com>,
	Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Subject: [GSOC] Update 5: Unification of tag -l, branch -l and for-each-ref
Date: Thu, 30 Jul 2015 21:34:19 +0530	[thread overview]
Message-ID: <CAOLa=ZTHe5Tw=CbhBJBeSD0yhwXyG3SOzNxy8zSxtYT+XWFh0w@mail.gmail.com> (raw)

Hello All,

As part of GSoC I'm working on the Unification of 'for-each-ref', 'tag -l'
and 'branch -l'.

Current Progress:

1. Building ref-filter.{c,h} from for-each-ref.
This is the process of creating an initial library for the unification
by moving most of the code from for-each-ref to ref-filter.{c,h}.
Merged into next

2. Add options to ref-filter.
This includes the porting of --points-at, --contains, --merged,
--no-merged options from builtin/branch.c and builtin/tag.c, Also the
implementation of these options into for-each-ref.
Currently in pu
(https://github.com/git/git/commit/6d4c958d88e6456405b8d65a8bf469382c47f4c5)

3. Port builtin/tag.c to use ref-filter.
Here we port tag.c to use ref-filter and also port the --format,
--sort and --merged and --no-merged options to builtin/tag.c.
Version 7 can be found here :
thread.gmane.org/gmane.comp.version-control.git/274990
We now have support for modifier atoms. Modifier atoms are atoms which
modify succeeding strings or atoms. A simple example of this is the "color"
atom which modifies the color of all succeeding atoms or strings.
Similarly we introduce "padright" atom which will align atoms and strings to the
left followed by spaces. This was after a lot on Input from Junio,
Matthieu, Christian, Duy, Eric and Jacob.
Currently waiting for review from the list.

4. Porting branch.c to use ref-filter.
Here we port branch.c to use ref-filter APIs.
An RFC version was sent to the list and can be found here :
article.gmane.org/gmane.comp.version-control.git/274766
There was a lot of input on this and we are still discussing the structure for
the "ifexists" atom. Currently everyone is indicating towards something like
--format="%(ifexists:<atom>) .............. %(endif).
This seems to be a good design and I hope to implement this over the
next 3 days and send an updated Patch series to the list. Also need to
implement show_ref_array_item() into branch.c. Currently we print form
branch.c itself.

Like always, Thanks to everyone for helping me out, especially my mentors.

All code pushed to github:
Github: https://github.com/KarthikNayak/git

-- 
Regards,
Karthik Nayak

             reply	other threads:[~2015-07-30 16:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 16:04 Karthik Nayak [this message]
2015-07-30 16:06 ` [GSOC] Update 5: Unification of tag -l, branch -l and for-each-ref Karthik Nayak
  -- strict thread matches above, loose matches on Subject: below --
2015-07-12 20:48 Karthik Nayak

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: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to='CAOLa=ZTHe5Tw=CbhBJBeSD0yhwXyG3SOzNxy8zSxtYT+XWFh0w@mail.gmail.com' \
    --to=karthik.188@gmail.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    /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://80x24.org/mirrors/git.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).