From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfstests: add local.config example
Date: Fri, 17 Sep 2010 09:31:45 +1000 [thread overview]
Message-ID: <20100916233145.GI24409@dastard> (raw)
In-Reply-To: <4C925CF3.3060303@sandeen.net>
On Thu, Sep 16, 2010 at 01:07:47PM -0500, Eric Sandeen wrote:
> I think it'd be useful to have a local.config template in the
> git repo, to avoid having to re-read the README each time
> to remember the required environment variable names.
>
> Thoughts? Am I just lazy? :)
Lazy makes the world go round. ;)
A template is probably a good idea.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
Btw, if you are going add a template, you might as well remove all
the old configs that are there. I don't think any of them exist
anymore, and they have no further use as templates.....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-16 23:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 18:07 [PATCH] xfstests: add local.config example Eric Sandeen
2010-09-16 23:31 ` Dave Chinner [this message]
2012-10-26 15:55 ` Rich Johnston
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=20100916233145.GI24409@dastard \
--to=david@fromorbit.com \
--cc=sandeen@sandeen.net \
--cc=xfs@oss.sgi.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