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

Re: [GSoC] Week 1: Unification of 'for-each-ref', 'tag -l' and 'branch -l'

From
Karthik Nayak <karthik.188@gmail.com>
Date
Jun 3, 2015, 16:42 UTC
Message-ID
<556F2E5A.90700@gmail.com>
In-Reply-To
<vpqh9qoepv1.fsf@anie.imag.fr>
On 06/03/2015 09:38 PM, Matthieu Moy wrote:
Show 11 quoted lines
> Karthik Nayak <karthik.188@gmail.com> writes:
>
>> 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
>
> Just to be clear: my advice is the above with "user" = "caller of the
> API", not "human being using Git". In other words, "git branch
> --contains" and "git tag --contains" would still be using two different
> algorithms, but the user wouldn't notice (except for performance).
>
Thanks for clearing that out, I should have said "caller of the API."
-- 
Regards,
Karthik
Previous: Matthieu MoyNext: Jeff King
Message 3 of 5 in “[GSoC] Week 1: Unification of 'for-each-ref', 'tag -l' and 'branch -l'”
  1. Karthik NayakJun 2, 2015
  2. Matthieu MoyJun 3, 2015
  3. Karthik NayakJun 3, 2015
  4. Jeff KingJun 3, 2015
  5. Karthik NayakJun 4, 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.