From: Theodore Ts'o <tytso@mit.edu>
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: Re: [PATCH] Subtract min_free_kbytes from dirtyable memory
Date: Sat, 26 Jan 2013 10:43:40 -0500 [thread overview]
Message-ID: <20130126154340.GC5887@thunk.org> (raw)
In-Reply-To: <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
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-01-26 15:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 9:53 [PATCH] Subtract min_free_kbytes from dirtyable memory paul.szabo
2013-01-25 13:01 ` Bug#695182: " Ben Hutchings
2013-01-25 23:49 ` paul.szabo
2013-01-26 0:10 ` Ben Hutchings
2013-01-26 3:05 ` paul.szabo
2013-01-26 3:07 ` paul.szabo
2013-01-26 3:17 ` Ben Hutchings
2013-01-26 0:14 ` Jonathan Nieder
2013-01-26 15:43 ` Theodore Ts'o [this message]
2013-01-26 7:44 ` Bug#695182: " Jonathan Nieder
2013-01-26 20:23 ` paul.szabo
2013-01-28 6:23 ` Minchan Kim
-- strict thread matches above, loose matches on Subject: below --
2013-01-21 3:15 paul.szabo
2013-01-21 17:49 ` Rik van Riel
2013-01-22 23:38 ` Andrew Morton
2013-01-23 1:49 ` Minchan Kim
2013-01-23 3:11 ` paul.szabo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130126154340.GC5887@thunk.org \
--to=tytso@mit.edu \
--cc=695182@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=jrnieder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=paul.szabo@sydney.edu.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).