From: Valerie Henson <val_henson@linux.intel.com>
Subject: [patch 0/1] Relative atime
Date: Fri, 25 Aug 2006 16:52:15 -0700
Message-ID: <20060825235215.820563000@linux.intel.com>
Cc: Akkana Peck <akkana@shallowsky.com>,
	Mark Fasheh <mark.fasheh@oracle.com>,
	Jesse Barnes <jesse.barnes@intel.com>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Chris Wedgewood <cw@foof.org>, jsipek@cs.sunysb.edu,
	Al Viro <viro@ftp.linux.org.uk>,
	Christoph Hellwig <hch@lst.de>, Adrian Bunk <bunk@stusta.de>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mga06.intel.com ([134.134.136.21]:48781 "EHLO
	orsmga101.jf.intel.com") by vger.kernel.org with ESMTP
	id S932236AbWHYXwj (ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Fri, 25 Aug 2006 19:52:39 -0400
To: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

There was enough interest in the relative atime patches that I went
ahead and implemented support in the mount command as well, and
cleaned up the patches for inclusion.  Relative atime only updates the
atime if the previous atime is older than the mtime or ctime.  It's
like noatime, but useful for applications like mutt that need to know
whether a file has been read since it was last modified.

-VAL