Ronnie Sahlberg <sahlb...@google.com> writes:
> ... The first
> backend will be the current files based structure but I also will add
> an optional backend using a TDB database.
I am assuming that as part of the transactions work, accesses to
reflogs will also have their own backends?
> You could then very easily create a new backend, say 'struct refs_be
> refs_files_case_insensitive' where the methods would just convert any
> refnames to/from a case insensitive encoding before invoking the
> default methods from the files backend.
> Perhaps something as simple as converting any upper case characters
> to/from '%xx' representation when accessing the actual files.
Hmm... that would work only when the new implementation of Git is
the only one that accesses the repository. Other implementations
(e.g. Eclipse via egit, Gerrit via jgit, etc.) peeking into the
same repository wouldn't know what to do with these encoded
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