public inbox for libabigail@sourceware.org
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: libabigail@sourceware.org, Dodji Seketeli <dodji@seketeli.org>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
	Matthias Maennich <maennich@google.com>
Subject: [PATCH] Further update 'make distcheck-fast'
Date: Tue, 14 Dec 2021 17:44:53 +0100	[thread overview]
Message-ID: <20211214164453.3237230-1-thomas@codesourcery.com> (raw)
In-Reply-To: <87a6h4qx9q.fsf@seketeli.org>

What got pushed in recent commit 497357cfd5793e5364a92080d9fae40cf94dc7dd
"Better highlight 'make distcheck-fast'" was the initial submission, before the
changes I made after Matthias Maennich's review.  So here they are again.

	* CONTRIBUTING: Further update 'make distcheck-fast'.

Suggested-by: Matthias Maennich <maennich@google.com>
Signed-off-by: Thomas Schwinge <thomas@codesourcery.com>
---
 CONTRIBUTING | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/CONTRIBUTING b/CONTRIBUTING
index f7cef0a8..24a483b2 100644
--- a/CONTRIBUTING
+++ b/CONTRIBUTING
@@ -72,7 +72,8 @@ there.
 Here, "make distcheck-fast" is a variant of the standard "make distcheck".
 It compresses with "--fast" instead of default "--best", and is
 significantly faster, given the size of the distribution.  You very likely
-want to use that one for local regression testing.
+want to use that one for local regression testing.  (However, don't use
+"make distcheck-fast" to create artifacts for distribution.)
 
 You can also launch this in parallel by doing:
 
@@ -91,7 +92,7 @@ into the ABIXML format and then compares the ABI internal
 representation gathered from the libabigail.so binary against the one
 gathered from the ABIXML format.  The two should be equal if
 everything goes right.  This is an important regression test.  The
-problem is that it can takes twice as much time as "make distcheck-fast".
+problem is that it can take a considerable amount of time.
 So we've put it into its own separate target.
 
 So, to be complete the regression checking command to run against your
-- 
2.25.1


  reply	other threads:[~2021-12-14 16:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 12:07 [PATCH] Better highlight " Thomas Schwinge
2021-12-09 12:13 ` Matthias Maennich
2021-12-09 21:38   ` Thomas Schwinge
2021-12-13 16:34     ` Dodji Seketeli
2021-12-14 16:44       ` Thomas Schwinge [this message]
2021-12-17 19:23         ` [PATCH] Further update " Dodji Seketeli

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=20211214164453.3237230-1-thomas@codesourcery.com \
    --to=thomas@codesourcery.com \
    --cc=dodji@seketeli.org \
    --cc=libabigail@sourceware.org \
    --cc=maennich@google.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 read-only IMAP folder(s) and NNTP newsgroup(s).