Jan Hudec wrote:
Ok, sounds reasonable.
With respect to the storage inside the tree, using a duplicate name with
mode 0 or a name with some kind of rare extension...
It should probably be investigated how much of the existing core needs
to be touched/changed to support the duplicate name.
I agree that using a custom rare extension would allow for almost no
change to git-core.
--
Sincerely,
Stephen R. van den Berg.
Real programmers don't produce results, they return exit codes.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg Kroah-Hartman | [PATCH 006/196] Chinese: add translation of oops-tracing.txt |
| Linus Torvalds | Linux 2.6.21-rc1 |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
| Alexey Dobriyan | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Evgeniy Polyakov | Re: [BUG] New Kernel Bugs |
git: | |
