git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[GSOC] Week 2: Unification of tag -l, branch -l and for-each-ref

From
karthik nayak <karthik.188@gmail.com>
Date
Jun 13, 2015, 20:40 UTC
Message-ID
<CAOLa=ZTYfrUyy4Z+xOwOH+KgWy2-0htkR5QdzNYUL4_5u-QioQ@mail.gmail.com>
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 two patches for review on the mailing list.

1. [PATCH v8 0/11] Create ref-filter from for-each-ref
(http://article.gmane.org/gmane.comp.version-control.git/271563)
This is basically related to the movement of code from for-each-ref to
ref-filter. ref-filter would act as a base for tag -l and branch -l. They can
eventually use the ref-filter APIs to implement the --format and --sort options
provided by ref-filter.
2. [PATCH v2 00/11] add options to for-each-ref
(http://article.gmane.org/gmane.comp.version-control.git/271575)
This relates to the addition of options like '--points-at',
'--merged', '--no-merged'
and '--contains' options to ref-filter and making use of these options
in for-each-ref
and implementing tests for the same.

Work in progress: You can follow my current progress on Github: https://github.com/KarthikNayak/git Currently working on bringing tag.c on board and making it use the ref-filter APIs and implement the various options provided by ref-filter. This might require an option of having ref-filter sort based on version no when listing refnames.

Whats next: After getting tag.c to work with ref-filter APIs. Start porting branch -l to use ref-filter APIs too.

-- 
Regards,
Karthik Nayak
Message 1 of 1 in “[GSOC] Week 2: Unification of tag -l, branch -l and for-each-ref”
  1. karthik nayakJun 13, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.