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

Re: [PATCH v5 02/12] ref-filter: use strbuf_split_str_omit_term()

From
Jeff King <peff@peff.net>
Date
Feb 16, 2016, 20:49 UTC
Message-ID
<20160216204954.GC27484@sigill.intra.peff.net>
In-Reply-To
<CAPig+cTiwHs+dD+jqAp8SNkwjQ2OzDsC8yopRgF7gctrGi5uUw@mail.gmail.com>
On Tue, Feb 16, 2016 at 03:12:29PM -0500, Eric Sunshine wrote:
Show 27 quoted lines
> > Did you consider just using string_list_split for this? AFAICT, you
> > don't care about the results being strbufs themselves, and it would do
> > what you want without having to bother with patch 1. [...]
> >
> > Sorry to waltz into a review of v5 with a suggestion to throw out all
> > the work done in previous iterations. :-/ I just think the strbuf_split
> > interface is kind of clunky and I'd be happy if we could slowly get rid
> > of it rather than growing it. [...]
> 
> That's a nice idea, however, I'm not sure if making it part of this
> series this late in the game is a good idea. The series has gone
> through major changes and heavy review in each of the preceding
> versions, and turnaround time has been consequently quite slow (due
> both to the amount of work required by Karthik for each version, and
> to the amount of time needed by reviewers to digest all the new
> changes). v4 was the first one which had settled to the point where
> only minor changes were needed, and we were hoping to land the series
> with v5. (A few larger changes were also discussed in v4 reviews, but
> we concluded that they could be done as follow-up patches.)
> 
> With that in mind, it might be better to make this change as a
> followup to this series. On the other hand, as you say, waiting would
> expand the strbuf_split interface undesirably, so the alternative
> would be for Karthik to submit v6 with this change only (to wit: drop
> patch 1 and rewrite patch 2 as you've shown). While such a change will
> again require careful review, at least it is well localized, and
> Karthik's turnaround time shouldn't be too bad. So...

Yeah, I don't insist, and like I said, I'm not 100% sure we can get rid of the strbuf_split interface anyway. I thought it might actually make things easier by making the series _shorter_ (so my regret was that mentioning earlier could have saved reviewing effort on patch 1).

It does mean extra review of the patch I posted, but my hope was that it's small and localized, and wouldn't impact the later stuff seriously (there are some textual tweaks to carry it forward, though).

Anyway, I've said my piece, and you guys can do what you will with it.
-Peff
Previous: Eric SunshineNext: Eric Sunshine
Message 7 of 32 in “ref-filter: use parsing functions”
  1. 00/12 ref-filter: use parsing functionsKarthik Nayak, Feb 16, 2016
  2. 01/12 strbuf: introduce strbuf_split_str_omit_term()Karthik Nayak, Feb 16, 2016
  3. 02/12 ref-filter: use strbuf_split_str_omit_term()Karthik Nayak, Feb 16, 2016
  4. Jeff KingFeb 16, 2016
  5. Jeff KingFeb 16, 2016
  6. Eric SunshineFeb 16, 2016
  7. Jeff KingFeb 16, 2016
  8. Eric SunshineFeb 16, 2016
  9. Jeff KingFeb 16, 2016
  10. Eric SunshineFeb 16, 2016
  11. Jeff KingFeb 16, 2016
  12. Junio C HamanoFeb 17, 2016
  13. Jeff KingFeb 17, 2016
  14. Junio C HamanoFeb 17, 2016
  15. Jeff KingFeb 17, 2016
  16. Junio C HamanoFeb 17, 2016
  17. Karthik NayakFeb 17, 2016
  18. Eric SunshineFeb 17, 2016
  19. Karthik NayakFeb 17, 2016
  20. Eric SunshineFeb 17, 2016
  21. Karthik NayakFeb 17, 2016
  22. Karthik NayakFeb 17, 2016
  23. 03/12 ref-filter: bump 'used_atom' and related code to the topKarthik Nayak, Feb 16, 2016
  24. 04/12 ref-filter: introduce struct used_atomKarthik Nayak, Feb 16, 2016
  25. 05/12 ref-filter: introduce parsing functions for each valid atomKarthik Nayak, Feb 16, 2016
  26. 06/12 ref-filter: introduce color_atom_parser()Karthik Nayak, Feb 16, 2016
  27. 07/12 ref-filter: introduce parse_align_position()Karthik Nayak, Feb 16, 2016
  28. 08/12 ref-filter: introduce align_atom_parser()Karthik Nayak, Feb 16, 2016
  29. 09/12 ref-filter: align: introduce long-form syntaxKarthik Nayak, Feb 16, 2016
  30. 10/12 ref-filter: introduce remote_ref_atom_parser()Karthik Nayak, Feb 16, 2016
  31. 11/12 ref-filter: introduce contents_atom_parser()Karthik Nayak, Feb 16, 2016
  32. 12/12 ref-filter: introduce objectname_atom_parser()Karthik Nayak, Feb 16, 2016

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.