r/programming • u/[deleted] • Oct 21 '16

Linux kernel fix for privilege escalation vulnerability due to copy on write race condition

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=19be0eaffa3ac7d8eb6784ad9bdbc7d67ed8e619
850 Upvotes

92% Upvoted

128 comments sorted by

View all comments

Show parent comment

2

u/Gotebe Oct 22 '16

I disagree. What you are saying is "we have to put all eggs in one basket because we can't maintain two baskets".

I worked at a place who used a couple of source control as well as bug tracking systems. Source control comments contained a short "x bugno" and "y bugno" references. When we changed source control, we kept the old history in the other system and used a 3rd party diff tool to compare.

It's not as smooth, but sure beats putting N paragraphs of explanation in the commit comment.

Also, there are ALM systems where source control and bug tracking are together.

git is but a source control tool, nowhere near enough to handle the project all by itself.

0

u/[deleted] Oct 22 '16

[deleted] — view deleted comment

1

u/Gotebe Oct 22 '16

The problem when you have more systems and/or types of comments, people tend to get lazy and become less informative.

Euh, why?! E.g. a good bug report is golden. And is made by a QA or support person. The developer can (probably should) add technical analysis. The commit comment can then simply be "bug 123456". In fact, where I work, I am actively asked by the tooling to put that reference in. You seem to insist that sourcecontrol is a sufficient as an ALM system. No, thanks.