On Thu, 11 Sep 2008, Stephen R. van den Berg wrote:... and therefore you might as well just have a separate file (which might or might not be tracked by git like the .gitignore files are) to keep that information? Since this is a rare operation, modifying the core database structure for this doesn't appear that appealing to most so far. And, while recording this origin link is optional, you are likely to make mistakes like forgotting to record it, or you might even wish to fix it with better links after the facts. Having it versionned also means that older git versions will be able to carry that information even if they won't make any use of it, and that also solves the cryptographic issue since that data is part of the top commit SHA1. Nicolas -- 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 KH | Og dreams of kernels |
| Jens Axboe | [PATCH 31/33] Fusion: sg chaining support |
| Arnd Bergmann | Re: finding your own dead "CONFIG_" variables |
| Mark Brown | [PATCH 2/2] Subject: natsemi: Allow users to disable workaround for DspCfg reset |
| Tony Breeds | [LGUEST] Look in object dir for .config |
git: | |
| Brian Downing | Re: Git in a Nutshell guide |
| John Benes | Re: master has some toys |
| Matthias Lederhofer | [PATCH 4/7] introduce GIT_WORK_TREE to specify the work tree |
| Alexander Sulfrian | [RFC/PATCH] RE: git calls SSH_ASKPASS even if DISPLAY is not set |
| Junio C Hamano | < |
