unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Carl Worth <cworth@cworth.org>
To: Keith Packard <keithp@keithp.com>,
	Adrian Perez <aperez@igalia.com>,
	notmuch@notmuchmail.org
Subject: Re: [PATCH] ANSI escapes in "new" only when output is a tty
Date: Thu, 26 Nov 2009 10:27:04 -0800	[thread overview]
Message-ID: <874oohrvk7.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <yuneinppubn.fsf@aiko.keithp.com>

On Sun, 22 Nov 2009 23:35:24 -0800, Keith Packard <keithp@keithp.com> wrote:
> Tracking directory mtime instead of just looking at the read-only bit
> would let us skip directories that haven't seen any change in content.

We've had directory mtime for a long time. I added the check for the
read-only bit afterwards to be able to avoid stats on a whole directory
hierarchy, (since mtime doesn't propagate upward of course).

> Tracking directory contents would let us easily detect name changes
> (add/remove/rename).

Do we want git tree objects for the directories? ...

-Carl

      reply	other threads:[~2009-11-26 18:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-23  0:54 [PATCH] ANSI escapes in "new" only when output is a tty Adrian Perez
2009-11-23  5:12 ` Carl Worth
2009-11-23  7:35   ` Keith Packard
2009-11-26 18:27     ` Carl Worth [this message]

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874oohrvk7.fsf@yoom.home.cworth.org \
    --to=cworth@cworth.org \
    --cc=aperez@igalia.com \
    --cc=keithp@keithp.com \
    --cc=notmuch@notmuchmail.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).