On Mon, Oct 21, 2013 at 9:02 PM, Johannes Sixt <j6t@xxxxxxxx> wrote: > Am 21.10.2013 03:31, schrieb Duy Nguyen: >> On Mon, Oct 21, 2013 at 12:57 AM, Antoine Pelisse <apelisse@xxxxxxxxx> wrote: >>> My main motive was to not *stop* the process when a long path is met. >>> Because somebody created a repository on Linux with a long file-name >>> doesn't mean you should not be able to clone it *at all* on Windows. >> >> That should be handled at the Windows compatibility layer if Windows >> cannot handle long paths as Linux > > Naah... PATH_MAX is a silly, arbitrary limit. The Git data model does > not forbid paths longer than PATH_MAX, be it 4096 or 260. A generic > solution is needed. > >> (or maybe at higher level to skip >> checking out those paths). > > More like this, yeah. I would argue that this is probably even a bug on Linux, only harder (if not impossible) to trigger by accident as there's probably no git-client that will generate such trees. But a "malicious" client might. -- 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