Conversation
Add a coding style document that tries to record the conventions that the project uses. It seemed more appropriate to put it up in the -kmod git repo context rather than in src/ which would end up in fs/scoutfs/ upstream. Signed-off-by: Zach Brown <zab@versity.com>
|
copying PR from PR against old repo I think the only question is exactly where to put it. Why not toplevel? |
Well, I'd first ask if we want it to begin with. It landed with a resounding thud when I first threw it together. Is it needed? |
|
Yeah I think it's a good idea. To just have a place to put style preferences. We may come up with more. I think I just read the PR and got the info that way but that's kinda cheating or something. |
|
Can one of the admins verify this patch? |
|
This won't automatically run in continuous integration without approval. A member of the Versity organization must allow it. |
|
This is ancient and I don't think we'll be doing this. |
3 participants
Add a coding style document that tries to record the conventions that
the project uses. It seemed more appropriate to put it up in the -kmod
git repo context rather than in src/ which would end up in fs/scoutfs/
upstream.
Signed-off-by: Zach Brown zab@versity.com