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: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
	Christian Couder <christian.couder@gmail.com>
Subject: [GSOC] Update 5: Unification of tag -l, branch -l and for-each-ref
Date: Mon, 13 Jul 2015 02:18:17 +0530	[thread overview]
Message-ID: <CAOLa=ZTg7j2S-E+wm3Jm9XqLraTZczP1goVZkiH9diFauho-6w@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'. Sorry for the lack of update since Jun 14, was a
little busy with an exam I had. Now thats over, I will be working more
on the project.

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 2 can be found here
http://thread.gmane.org/gmane.comp.version-control.git/273731
A lot of input on this, Junio and Duy gave some suggestions on
how we can align items in the format option, there has been good progress
in this regard. More at
http://thread.gmane.org/gmane.comp.version-control.git/273732. A
working prototype of these suggestions have been pushed to Github,
where suggestions can be made until I send my next iteration of the
patch series.
Also a lot of changes suggested by my mentors Matthieu and Christian. Most of
which have been implemented and pushed to Github.

Next:
Have been working on branch.c and there is good progress for the same.
Code pushed to Github.

Github: https://github.com/KarthikNayak/git

Thanks to everyone who has helped :)

-- 
Regards,
Karthik Nayak

             reply	other threads:[~2015-07-12 20:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-12 20:48 Karthik Nayak [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-07-30 16:04 [GSOC] Update 5: Unification of tag -l, branch -l and for-each-ref Karthik Nayak
2015-07-30 16:06 ` 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=ZTg7j2S-E+wm3Jm9XqLraTZczP1goVZkiH9diFauho-6w@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).