Bug#695182: [PATCH] Subtract min_free_kbytes from dirtyable memory
- To: Jonathan Nieder <jrnieder@gmail.com>
- Cc: paul.szabo@sydney.edu.au, 695182@bugs.debian.org, ben@decadent.org.uk, linux-kernel@vger.kernel.org, linux-mm@kvack.org, minchan@kernel.org
- Subject: Bug#695182: [PATCH] Subtract min_free_kbytes from dirtyable memory
- From: Theodore Ts'o <tytso@mit.edu>
- Date: Sat, 26 Jan 2013 10:43:40 -0500
- Message-id: <[🔎] 20130126154340.GC5887@thunk.org>
- Mail-followup-to: Theodore Ts'o <tytso@mit.edu>, Jonathan Nieder <jrnieder@gmail.com>, paul.szabo@sydney.edu.au, 695182@bugs.debian.org, ben@decadent.org.uk, linux-kernel@vger.kernel.org, linux-mm@kvack.org, minchan@kernel.org
- Reply-to: Theodore Ts'o <tytso@mit.edu>, 695182@bugs.debian.org
- In-reply-to: <[🔎] 20130126001419.GG3341@elie.Belkin>
- References: <[🔎] 1359118913.3146.3.camel@deadeye.wl.decadent.org.uk> <[🔎] 201301252349.r0PNnFYF024399@como.maths.usyd.edu.au> <[🔎] 20130126001419.GG3341@elie.Belkin>
(In the teach a person to fish category...)
If you know the file and line number where a bug/regression was
introduced, the "git blame" command is a great tool for identifying
the commit which changed a given line of code. Then use "git tag
--contains <commit it>" to see when a particular commit was introduced
into the mainline kernel.
- Ted
Reply to: