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

Re: [PATCH] check_refname_component: Optimize

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
May 31, 2014, 10:47 UTC
Message-ID
<5389B35C.8060308@alum.mit.edu>
In-Reply-To
<20140530172944.GC25443@sigill.intra.peff.net>
On 05/30/2014 07:29 PM, Jeff King wrote:
Show 9 quoted lines
> On Fri, May 30, 2014 at 11:47:33AM +0200, Michael Haggerty wrote:
>> [...]
>> If we want to be robust to future changes to refname rules, we could add
>> a header flag like
>>
>>     # pack-refs with: peeled fully-peeled check-level=1.0
> [...]
> Yeah, I thought about mentioning something like that. But really, this
> just seems like a lot of complexity to solve the problem in a wrong way.
Yes, you are right.
Michael
-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/
Previous: Jeff KingNext: Duy Nguyen
Message 14 of 15 in “check_refname_component: Optimize”
  1. 0/1 check_refname_component: OptimizeDavid Turner, May 28, 2014
  2. check_refname_component: OptimizeDavid Turner, May 28, 2014
  3. Michael HaggertyMay 28, 2014
  4. David TurnerMay 28, 2014
  5. Duy NguyenMay 29, 2014
  6. Junio C HamanoMay 29, 2014
  7. Duy NguyenMay 29, 2014
  8. Jeff KingMay 29, 2014
  9. Duy NguyenMay 29, 2014
  10. Jeff KingMay 30, 2014
  11. Duy NguyenMay 30, 2014
  12. Michael HaggertyMay 30, 2014
  13. Jeff KingMay 30, 2014
  14. Michael HaggertyMay 31, 2014
  15. Duy NguyenMay 31, 2014

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.