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

Re: [PATCH v2 04/10] ref-filter: add support to sort by version

From
Karthik Nayak <karthik.188@gmail.com>
Date
Jul 11, 2015, 05:54 UTC
Message-ID
<CAOLa=ZSuftULFSCKK=PoaPejA_FXGkmVrOybk1G6OEjDchfSEg@mail.gmail.com>
In-Reply-To
<vpqd2005hq4.fsf@anie.imag.fr>

On Fri, Jul 10, 2015 at 5:48 PM, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:

Show 30 quoted lines
> Karthik Nayak <karthik.188@gmail.com> writes:
>
>> On Fri, Jul 10, 2015 at 4:22 PM, Karthik Nayak <karthik.188@gmail.com> wrote:
>>> On Thu, Jul 9, 2015 at 6:59 PM, Matthieu Moy
>>> <Matthieu.Moy@grenoble-inp.fr> wrote:
>>>> Karthik Nayak <karthik.188@gmail.com> writes:
>>>>
>>>>> Add support to sort by version using the "v:refname" and
>>>>> "version:refname" option. This is achieved by using the
>>>>> 'version_cmp()' function as the comparing function for qsort.
>>>>
>>>> You should elaborate on why you need this. Given the context, I can
>>>> guess that you will need this to implement tag, but for example I first
>>>> wondered why you needed both version: and v:, but I guess it comes from
>>>> the fact that 'git tag --sort' can take version:refname or v:refname.
>>>>
>>>> I think this deserves a test and documentation in for-each-ref.txt.
>>>
>>> I'll add it to "for-each-ref.txt" documentation.
>>> About the tests, there are already tests for the same in git-tag.txt and
>>> that's the only reason I did not repeat the tests in for-each-ref.
>>>
>>
>> But since the porting is in a later commit, will add tests to for-each-ref.
>
> Yes: to me "it's tested through 'git tag'" is a good argument to do only
> a superficial test, check that 'for-each-ref --sort v:refname' activate
> the sorting, but no detailed corner-case testing. But not a good
> argument to have no test at all on for-each-ref.
>
Agreed, I've written tests for the same.
-- 
Regards,
Karthik Nayak
Previous: Matthieu MoyNext: Karthik Nayak
Message 12 of 48 in “Port tag.c to use ref-filter APIs”
  1. 00/10 Port tag.c to use ref-filter APIsKarthik Nayak, Jul 9, 2015
  2. 01/10 ref-filter: add %(refname:shortalign=X) optionKarthik Nayak, Jul 9, 2015
  3. 02/10 ref-filter: add option to filter only tagsKarthik Nayak, Jul 9, 2015
  4. 03/10 ref-filter: support printing N lines from tag annotationKarthik Nayak, Jul 9, 2015
  5. Matthieu MoyJul 9, 2015
  6. Karthik NayakJul 10, 2015
  7. 04/10 ref-filter: add support to sort by versionKarthik Nayak, Jul 9, 2015
  8. Matthieu MoyJul 9, 2015
  9. Karthik NayakJul 10, 2015
  10. Karthik NayakJul 10, 2015
  11. Matthieu MoyJul 10, 2015
  12. Karthik NayakJul 11, 2015
  13. 05/10 ref-filter: add option to match literal patternKarthik Nayak, Jul 9, 2015
  14. Matthieu MoyJul 9, 2015
  15. Karthik NayakJul 10, 2015
  16. Junio C HamanoJul 10, 2015
  17. Karthik NayakJul 11, 2015
  18. Matthieu MoyJul 11, 2015
  19. Karthik NayakJul 11, 2015
  20. 06/10 Documentation/tag: remove double occurance of "<pattern>"Karthik Nayak, Jul 9, 2015
  21. Christian CouderJul 9, 2015
  22. Karthik NayakJul 9, 2015
  23. Junio C HamanoJul 10, 2015
  24. Karthik NayakJul 12, 2015
  25. 07/10 tag.c: use 'ref-filter' data structuresKarthik Nayak, Jul 9, 2015
  26. 08/10 tag.c: use 'ref-filter' APIsKarthik Nayak, Jul 9, 2015
  27. Matthieu MoyJul 9, 2015
  28. Karthik NayakJul 9, 2015
  29. Matthieu MoyJul 9, 2015
  30. Karthik NayakJul 10, 2015
  31. Matthieu MoyJul 9, 2015
  32. 08/10 tag.c: use 'ref-filter' APIsKarthik Nayak, Jul 9, 2015
  33. Duy NguyenJul 12, 2015
  34. Karthik NayakJul 12, 2015
  35. Duy NguyenJul 13, 2015
  36. Karthik NayakJul 13, 2015
  37. 09/10 tag.c: implement '--format' optionKarthik Nayak, Jul 9, 2015
  38. 10/10 tag.c: implement '--merged' and '--no-merged' optionsKarthik Nayak, Jul 9, 2015
  39. Matthieu MoyJul 9, 2015
  40. Karthik NayakJul 11, 2015
  41. Matthieu MoyJul 11, 2015
  42. Junio C HamanoJul 10, 2015
  43. Karthik NayakJul 11, 2015
  44. Duy NguyenJul 12, 2015
  45. Duy NguyenJul 12, 2015
  46. Karthik NayakJul 12, 2015
  47. Duy NguyenJul 13, 2015
  48. Karthik NayakJul 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.