linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] e2fsprogs: fix configure.in typo
Date: Wed, 21 Oct 2009 18:19:32 -0400	[thread overview]
Message-ID: <20091021221932.GC20619@mit.edu> (raw)
In-Reply-To: <4ADF87B9.3040204@redhat.com>

On Wed, Oct 21, 2009 at 05:14:17PM -0500, Eric Sandeen wrote:
> oh dear, maybe that's it :)
> 
> Ok, on a fresh checkout it worked...
> 
> Sorry, not sure what state I got things into.

Git status should have shown the "extra" file; I make a practice of
using "git status" often to make sure there aren't any files I forgot
to check in, or anything other unexpected discrepancies between the
head of the git tree and the working directory.

					- Ted

      reply	other threads:[~2009-10-21 22:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21  3:48 [PATCH] e2fsprogs: fix configure.in typo Eric Sandeen
2009-10-21  7:52 ` Theodore Tso
2009-10-21 15:21   ` Eric Sandeen
2009-10-21 21:57     ` Theodore Tso
2009-10-21 22:14       ` Eric Sandeen
2009-10-21 22:19         ` Theodore Tso [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

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

  git send-email \
    --in-reply-to=20091021221932.GC20619@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    /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).