Duy Nguyen <pclouds@xxxxxxxxx> writes: > This one, on the other hand, changes the "shape" of the repo (now with > holes) and might need to go through the same process we do with this > series. Maybe we should prepare for it now. Do you have a use case for > size-based filtering? What can we do with a repo with some arbitrary > blobs missing? Another form of this is narrow clone, where we cut by > paths, not by blob size. Narrow clone sounds more useful to me because > it's easier to control what we leave out. I was about to say "Hear, hear", but then stopped with a question to myself: why are these "some people do not want them" paths in the same repository in the first place? -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html