Johannes Schindelin <Johannes.Schindelin@gmx.de> writes: >> > - disallow fetching from this repo, and >> >> Why? It's perfectly acceptable to pull from an incomplete >> repo, as long as you don't care about the old history. > > Right. But should that be the default? I don't think so. Therefore: > disable it, and if the user is absolutely sure to do dumb things, she'll > have to enable it explicitely. If the downstream person wants to have a shallow history of post X.org X server core to further hack on it, I do not think of a reason why we would want to refuse her from cloning a repository of a fellow developer who has already done such a shallow copy. If such a clone is done without telling the downstream that the result is a shallow one, it is "dumb". I would agree it should not be done. We need to propagate the grafts to the downstream when a clone is done because of this. By the way, please refrain from discussing .git/config vs .git/eparate-config-files issue in this thread. My personal feeling so far is that the information current graft represents is good enough to support shallow clones, and if not we can extend its semantics to support such. It can be discussed independently if it is a good idea to move the final result (grafts with updated semantics) to config file. Even if we end up not doing any of the shallow cloning support we have been discussing, moving the information in .git/info/grafts to config might make sense. The issue is tangential. - 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.htmlReceived on Tue Jan 31 06:26:00 2006
This archive was generated by hypermail 2.1.8 : 2006-01-31 06:27:10 EST