Excerpts from Junio C Hamano's message of Thu Sep 06 21:33:20 -0400 2012:
> > identifiers generated from keys like:
> > url./some/really/long/path.insteadOf
> > could overrun the current limit. It's not a common case, of course,
> > or this issue would have been found sooner. Would doubling the
> > current limit be out of the question?
> Is there a reason to have _any_ limitation? It is not like we store
> configuration data by allocating one file per item (in which case we
> may be limited by the filesystem limit for direntry size), so if it
> is not too much trouble, I think the right thing to do is to lift
> the limitation altogether, possibly using strbuf instead of a
> statically sized array of characters.
I thought it made sense to impose some sort of bound here but removing
the limit wouldn't encourage the use of ridiculously long names so
lifting it entirely shouldn't hurt.
Any chosen limit would always be somewhat arbitrary. I had considered
extending it to (PATHMAX + x) where x would also be arbitrary as
that would allow any valid url./path/max.insteadOf type setting but
that didn't seem like a good approach.
Removing the limit is a much better choice...
> Of course, once you write a very long entry using a newer version of
> Git, the resulting configuration file may end up unusable by older
> version of Git, so a patch to implement such a change may need to be
> based on older maintenance release (say maint-1.7.9) and then merged
> upwards, but otherwise I do not offhand see a compatibility downside
> of such a change.
I'm ok with this approach and will put an altered patch together
shortly. I think it's fairly unlikely, but not impossible, that
anyone creating a config file with long key names would be in a
situation where someone else couldn't read that same config file.
I'll still base the change on maint-1.7.9 as suggested though.
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html