From: Junio C Hamano <gitster@pobox.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: GIT Mailing-list <git@vger.kernel.org>,
Pratyush Yadav <me@yadavpratyush.com>,
Adam Dinwoodie <adam@dinwoodie.org>
Subject: Re: [RFC PATCH 0/8] speed up 'make clean'
Date: Thu, 05 Nov 2020 13:48:29 -0800 [thread overview]
Message-ID: <xmqq361niifm.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <e1d218bb-7658-565e-0931-2411efbb561c@ramsayjones.plus.com> (Ramsay Jones's message of "Thu, 5 Nov 2020 21:01:08 +0000")
Ramsay Jones <ramsay@ramsayjones.plus.com> writes:
> [Yes, 'cd Documentation; make clean all' will be slower that a doing
> separate 'make clean; make', but the extra 10s, or so, will be swamped
> by the documentation build time! ;-) ]
Hmph, the "all" part in "make clean all" needs the information we
read from these generated files, and time must be spent to generate
them whether "make clean all" or "make clean; make all" is used. In
the latter, we may not generate and read them in the first phase,
but the second one "make all" would need to do so anyway. So I am
puzzled why "make clean all" needs to be slower---don't we generate
and read them only once in either case?
next prev parent reply other threads:[~2020-11-05 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 21:01 [RFC PATCH 0/8] speed up 'make clean' Ramsay Jones
2020-11-05 21:48 ` Junio C Hamano [this message]
2020-11-06 1:26 ` Ramsay Jones
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq361niifm.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=adam@dinwoodie.org \
--cc=git@vger.kernel.org \
--cc=me@yadavpratyush.com \
--cc=ramsay@ramsayjones.plus.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.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).