linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: What's cooking in e2fsprogs.git (topics)
Date: Wed, 20 Feb 2008 12:46:57 -0600	[thread overview]
Message-ID: <47BC75A1.10605@redhat.com> (raw)
In-Reply-To: <20080219050945.GU25098@mit.edu>

Theodore Tso wrote:
> The big news here is that extents branch is sufficiently finished that
> I've promoted it to the next branch.

Hey, that's great news.  :)

Out of curiosity; what is the plan for behavior when finding symlinks
with the extents flag set?  Last I checked e2fsprogs-interim, they got
clobbered.  Is that on the TODO before extents support goes "live?"

Thanks,
-Eric

  reply	other threads:[~2008-02-20 18:47 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-04 22:42 What's cooking in e2fsprogs.git (topics) Theodore Ts'o, Theodore Ts'o
2007-11-05  2:15 ` Andreas Dilger
2007-11-05  4:32   ` Theodore Tso
2007-11-05 15:06     ` Andreas Dilger
2007-12-17 17:11 ` Theodore Tso
2007-12-17 22:34   ` Andreas Dilger
2007-12-17 22:59     ` Theodore Tso
2007-12-17 23:36       ` Andreas Dilger
2007-12-18  3:32         ` Theodore Tso
2007-12-18  8:13       ` Florian Weimer
2007-12-18 19:10   ` What's cooking in e2fsprogs.git (topics) - [RFC] FLEX_BG bmap and itable allocation patch Jose R. Santos
2008-02-11  4:51   ` What's cooking in e2fsprogs.git (topics) Theodore Tso
2008-02-11  5:08     ` Eric Sandeen
2008-02-11  7:24       ` Theodore Tso
2008-02-19  5:09     ` Theodore Tso
2008-02-20 18:46       ` Eric Sandeen [this message]
2008-02-21 14:05         ` Theodore Tso
2008-02-21 16:40           ` Eric Sandeen
2008-02-22 23:14             ` Andreas Dilger
2008-02-23  0:15               ` Theodore Tso
2008-02-25  4:20                 ` Andreas Dilger
2008-02-25 15:13                   ` Theodore Tso
2008-02-25 16:01                     ` Aneesh Kumar K.V
2008-02-25 17:32                     ` Eric Sandeen
2008-02-25 20:23                       ` Theodore Tso
2008-02-29 15:43       ` Theodore Tso
2008-02-29 19:59         ` Andreas Dilger
2008-02-29 22:49           ` Theodore Tso
2008-03-02  3:24         ` Jose R. Santos
2008-03-05 16:59         ` Jose R. Santos
2008-03-13 18:11         ` Theodore Tso
2008-03-20 20:32           ` Theodore Tso
2008-04-02  0:09         ` Theodore Tso
2008-04-07 17:12           ` Theodore Tso
2008-04-18 18:43             ` Theodore Tso
2008-04-21 16:41               ` Theodore Tso
2008-04-23  7:32                 ` Aneesh Kumar K.V
2008-04-23 11:55                   ` Theodore Tso
2008-04-23 18:58                 ` Aneesh Kumar K.V
2008-04-28 19:44                   ` The changes I made to the undo-mgr (Re: What's cooking in e2fsprogs.git (topics)) Theodore Tso
2008-05-24 23:54                 ` What's cooking in e2fsprogs.git (topics) Theodore Tso
2008-06-03  2:40                   ` Theodore Tso
2008-06-17 12:03                     ` Theodore Tso
2008-03-02 23:50       ` Christian Kujau
  -- strict thread matches above, loose matches on Subject: below --
2007-10-16  4:48 Theodore Ts'o
2007-10-16  5:36 ` Aneesh Kumar K.V
2007-10-16 16:41 ` Jose R. Santos

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=47BC75A1.10605@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).