From: Carl Worth <cworth@cworth.org>
To: david@tethera.net, notmuch@notmuchmail.org
Cc: David Bremner <bremner@debian.org>
Subject: Re: [PATCH] libnotmuch: fix typos in CLEAN setting, add file
Date: Tue, 28 Jun 2011 11:55:20 -0700 [thread overview]
Message-ID: <87liwlaiqv.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <1309005958-10409-1-git-send-email-david@tethera.net>
[-- Attachment #1: Type: text/plain, Size: 1521 bytes --]
On Sat, 25 Jun 2011 09:45:58 -0300, david@tethera.net wrote:
> Here is an updated version.
Thanks. I've committed this now, (waiting to be pushed until I fix my
build---the symbols stuff---so I can actually run "make test" again).
> I'm not sure the best way to do a test of
> the cleaning; maybe we should ship a MANIFEST file containing the
> output of git ls-files. I'm not sure how much churn this would cause
> in git. Perhaps it could be treated like version, and generated from
> git if possible.
Definitely wouldn't want a generated file under revision control. It
would be possible to just run "git ls-files" if we're in a git
repository and skip the test otherwise. Or...
> In any case I guess this couldn't really be part of
> our regular test suite, because all the other tests would fail ;).
Heh, that would be a bad failure mode. :-)
The typical way to do this (as far as I understand) is as part of "make
distcheck". The idea there is to make a tar file; verify that the tar
file can be unpacked, configured, built, and installed; and then to
verify that "make distclean" returns the directory to the same state as
just after having unpacked the tar file.
I'm not really all that concerned about it though. We don't add/remove
files all that often, and it's generally not too bad of a failure mode
if "make clean" isn't perfect.
So if someone added testing for this, that would be fine, but it's not a
high priority for me.
-Carl
--
carl.d.worth@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2011-06-28 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 10:53 [PATCH] libnotmuch: fix typo in CLEAN setting, add file david
2011-06-24 17:51 ` Carl Worth
2011-06-25 12:45 ` [PATCH] libnotmuch: fix typos " david
2011-06-28 18:55 ` 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=87liwlaiqv.fsf@yoom.home.cworth.org \
--to=cworth@cworth.org \
--cc=bremner@debian.org \
--cc=david@tethera.net \
--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).