On Tue, Jul 11, 2017 at 11:10 AM, Nikolay Shustov <nikolay.shustov@xxxxxxxxx> wrote: > Thank you for the explanation. The example about backend and frontend > is relevant even though I normally have to deal with more layers at > the same time. > > However, in my case I have the thing that you have already tried to > address, partially: the changes always align with file boundaries BUT > not with directory boundaries. Imagine you have the stack of backend, > data transport and frontend layers. The feature has to touch all three > layers thus resulting in the changes in the apparently different > directories. Thus, making the distinction by the pathspec (if I > understood it right from reading the documentation) would not help. > > The attributes could be a solution, if I could: > 1. create attribute designated to the feature > 2. "mark" uncommitted files in different directory with that attribute 1+2 should be answered by the gitattributes man page https://git-scm.com/docs/gitattributes > 3. filter the list of unchanged files with such attribute This sounds like one of "git status :(attr:backend) ." "git status :(exclude,attr:backend) ." > 4. create commit for the files only with the certain attribute > > You've kindly demonstrated that #4 is doable; however I could not > clearly get for the Git documentation if #1 - #3 are achievable... > Could you point me to the right place in the documentation, please? >
