From mboxrd@z Thu Jan  1 00:00:00 1970
From: Chris Mason <chris.mason@oracle.com>
Subject: Re: btrfs subvol find-modified
Date: Fri, 26 Mar 2010 16:26:46 -0400
Message-ID: <20100326202646.GG13680@think>
References: <20100326111807.24dcc2f0@simplux>
 <20100326132219.GF16453@think>
 <20100326195147.146db06e@simplux>
 <20100326193642.GC13680@think>
 <20100326212207.424db8af@simplux>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: linux-btrfs@vger.kernel.org
To: "Dipl.-Ing. Michael Niederle" <mniederle@gmx.at>
Return-path: <linux-btrfs-owner@vger.kernel.org>
In-Reply-To: <20100326212207.424db8af@simplux>
List-ID: <linux-btrfs.vger.kernel.org>

On Fri, Mar 26, 2010 at 09:22:07PM +0100, Dipl.-Ing. Michael Niederle wrote:
> Hi, Chris!
> 
> > Add an optional timestamp field to filter
> > files that have changed since a given timestamp.
> 
> Is there a possibility to derive the timestamp directly from the generation
> number?

I'm afraid not.

> 
> If we have a "-e"-switch for printing extent-information we could also have
> another switch to decide whether to print directory-information or not and
> combine find-new and find-modified into a single command.

Yes, that's the direction I'd like to see.

> 
> Meanwhile I have implemented the (very simple) command
> 
> btrfs subvolume max-gen <path>
> 	Print the highest generation number in a filesystem.
> 

Great.

-chris