Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > On Wed, 25 May 2016, Junio C Hamano wrote: > >> * I am not familiar with life on filesystems with core.filemode=0; >> do files people would want to be able to "add --chmod=+x" share >> common trait that can be expressed with .gitattributes mechanism? > > I think it is safe to say that the biggest example of core.filemode == 0 > is Windows. On that platform, there simply is no executable bit in the > sense of POSIX permissions. ... > ... I still like Ed's idea and would love to have it: it is murky waters to > require users to call plumbing only because our porcelain isn't up to par. I thought that I made it absolutely clear that I like the addition, too. If it wasn't clear enough, I can say it again, but I do not think you need it ;-). The "attribute" thing was an idea that was hoping to make the system as a whole even more helpful; if pattern matching with paths is sufficient for projects to hint desired permission bits per paths, then those working on such a cross-platform project on Windows do not have to even worry about "git cmd --chmod=+x", whether cmd is add or update-index. If they can just do "git add" and need to use the new "--chmod=+x" option only when the patterns are not set up correctly, wouldn't that be even more helpful? In other words, it wasn't "with this we can _eliminate_ need for 'add --chmod'". The only thing I was unsure about that scheme was if "pattern matching with paths" is sufficiently powerful (if not, such an addition would not work as a mechanism to reduce the need for the users to run "git add --chmod=+x"). And that was my inquiry. Unfortunately, your answer does not help answer that question; it was a question to Edward, so that's OK anyway. -- 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