All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karthik Nayak <karthik.188@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Christian Couder <christian.couder@gmail.com>,
	Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Subject: [GSoC] Week 1: Unification of 'for-each-ref', 'tag -l' and 'branch -l'
Date: Tue, 02 Jun 2015 22:08:57 +0530	[thread overview]
Message-ID: <556DDC21.5050801@gmail.com> (raw)

Hello All,

As part of GSoC I'm working on the Unification of 'for-each-ref', 'tag -l'
and 'branch -l'. I will update the list on my weekly progress in an effort
to keep everyone updated.

Current Progress:
Currently I have been working on moving all code from 'for-each-ref' to an
independent library called 'ref-filter' which would serve as a common 
library
for the unification process. 'for-each-ref' supports printing the commits
in a specified format and also various sorting optins. This would serve as a
good base for porting over these options for 'tag -l' and 'branch -l'.
I have sent v4 of my patch to the list and it can be found here:
http://article.gmane.org/gmane.comp.version-control.git/270293
I have been working on this after suggested changes, will post the next
version soon.

Work In progress:
You can follow my current progress on Github:
https://github.com/KarthikNayak/git
For now I got the '--points-at' option (prints only refs pointing to given
commit) and also '--merged' option (prints only refs whose heads are 
reachable
from the given commit). These shall be forwarded to the list soon.

What to do next:
Implement '--contains' option, but the problem to be faced here is that both
'tag -l' and 'branch -l' have different implementations of the '--contains'
options.  Matthieu Moy suggested that I work on the unification of these 
commands
let both the implementations stay where the user can select the 
implementation
to be used and that I may work on unification of these two algorithms after
the main objective of GSoC is met.

Any suggestion/changes are welcome.

-- 
Regards,
Karthik

             reply	other threads:[~2015-06-02 16:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02 16:38 Karthik Nayak [this message]
2015-06-03 16:08 ` [GSoC] Week 1: Unification of 'for-each-ref', 'tag -l' and 'branch -l' Matthieu Moy
2015-06-03 16:42   ` Karthik Nayak
2015-06-03 21:08   ` Jeff King
2015-06-04  7:35     ` 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

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

  git send-email \
    --in-reply-to=556DDC21.5050801@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.
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.