Re: [PATCH v7 19/28] files-backend: replace submodule_allowed check in files_downcast()

On Fri, Apr 14, 2017 at 03:44:46AM -0700, Junio C Hamano wrote: > Duy Nguyen writes: > > > I'll mark this mail and do a follow-up patch once this topic graduates > > to master. It's less review burden and mail traffic. > > I actually do not mind a single replacement patch.

Re: [PATCH v7 19/28] files-backend: replace submodule_allowed check in files_downcast()

Duy Nguyen writes: > I'll mark this mail and do a follow-up patch once this topic graduates > to master. It's less review burden and mail traffic. I actually do not mind a single replacement patch.

Re: [PATCH v7 19/28] files-backend: replace submodule_allowed check in files_downcast()

I'll mark this mail and do a follow-up patch once this topic graduates to master. It's less review burden and mail traffic. On Sat, Apr 1, 2017 at 11:02 AM, Michael Haggerty wrote: > On 03/26/2017 04:42 AM, Nguyễn Thái Ngọc Duy wrote: >> files-backend.c is unlearning

Re: [PATCH v7 19/28] files-backend: replace submodule_allowed check in files_downcast()

On 03/26/2017 04:42 AM, Nguyễn Thái Ngọc Duy wrote: > files-backend.c is unlearning submodules. Instead of having a specific > check for submodules to see what operation is allowed, files backend > now takes a set of flags at init. Each operation will check if the > required flags is present

[PATCH v7 19/28] files-backend: replace submodule_allowed check in files_downcast()

files-backend.c is unlearning submodules. Instead of having a specific check for submodules to see what operation is allowed, files backend now takes a set of flags at init. Each operation will check if the required flags is present before performing. For now we have four flags: read, write and