Jeff King p...@peff.net writes:
On Sat, Mar 01, 2014 at 12:01:44PM +0100, Matthieu Moy wrote:
Jeff King p...@peff.net writes:
If we had the keys in-memory, we could reverse this: config code asks
for keys it cares about, and we can do an optimized lookup (binary
search, hash, etc).
On Sat, Mar 01, 2014 at 12:01:44PM +0100, Matthieu Moy wrote:
Jeff King p...@peff.net writes:
If we had the keys in-memory, we could reverse this: config code asks
for keys it cares about, and we can do an optimized lookup (binary
search, hash, etc).
I'm actually dreaming of a system
Jeff King p...@peff.net writes:
Most callbacks would convert to a query system in a pretty
straightforward way, but some that have side effects might be tricky.
Converting them all may be too large for a GSoC project, but I think you
could do it gradually:
1. Convert the parser to read
Jeff King p...@peff.net writes:
If we had the keys in-memory, we could reverse this: config code asks
for keys it cares about, and we can do an optimized lookup (binary
search, hash, etc).
I'm actually dreaming of a system where a configuration variable could
be declared in Git's source code,
I just wrote up another double-idea that has been stewing in my head for
a while:
* Allow configuration values to be unset via a config file
* Fix git config --unset to clean up detritus from sections that are
left empty.
These ideas are more out there than the last, and might be too
Michael Haggerty mhag...@alum.mit.edu writes:
I just wrote up another double-idea that has been stewing in my head for
a while:
* Allow configuration values to be unset via a config file
* Fix git config --unset to clean up detritus from sections that are
left empty.
The former is *way*
On 02/28/2014 09:00 PM, Junio C Hamano wrote:
Michael Haggerty mhag...@alum.mit.edu writes:
I just wrote up another double-idea that has been stewing in my head for
a while:
* Allow configuration values to be unset via a config file
* Fix git config --unset to clean up detritus from
On Sat, Mar 01, 2014 at 01:19:32AM +0100, Michael Haggerty wrote:
I absolutely understand that changing all of the config parsers is not
feasible. But I had imagined a third route:
(3) parse the config once, storing the raw values to records in
memory. When an unset is seen, delete
8 matches
Mail list logo
