From: Eli Zaretskii <eliz@gnu.org>
To: Tim Cross <theophilusx@gmail.com>
Cc: rgm@gnu.org, larsi@gnus.org, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: extraclean and admin/grammars [was Re: Git master head build failure?]
Date: Sun, 04 Apr 2021 10:39:26 +0300 [thread overview]
Message-ID: <838s5yebwx.fsf@gnu.org> (raw)
In-Reply-To: <CAC=50j-CBeOj+oQptOafTyMbS+OrppgHdhXatA2mrghckB8Eeg@mail.gmail.com> (message from Tim Cross on Sun, 4 Apr 2021 09:52:31 +1000)
> From: Tim Cross <theophilusx@gmail.com>
> Date: Sun, 4 Apr 2021 09:52:31 +1000
> Cc: Glenn Morris <rgm@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>,
> Stefan Monnier <monnier@iro.umontreal.ca>,
> Emacs developers <emacs-devel@gnu.org>
>
> On Sun, 4 Apr 2021 at 01:15, Eli Zaretskii <eliz@gnu.org> wrote:
>
> "make extraclean" is only needed when doing something very drastic,
> like switching to a very different branch. That is an extremely rare
> (if not improbable) use case, so IMO having everyone pay for it is
> unjustified.
>
> I'm not sure that assumption is correct. You can run into this issue just changing commits, not switching
> branches if that commit is old enough. For example, checking out the emacs-27 tag. I'm also not convinced
> moving between the last released version and the current development version and back again is that
> unusual and the longer things go between the last release and current development head, the larger the
> difference in commits and greater the potential for this sort of issue.
It isn't an assumption: I'm doing all of the above all the time.
Switching between branches in Emacs is not recommended, because they
diverge very quickly. If you must do that, "make extraclean" is the
way to go.
next prev parent reply other threads:[~2021-04-04 7:39 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 2:41 Git master head build failure? Tim Cross
2021-04-01 3:04 ` Stefan Monnier
2021-04-01 3:10 ` Tim Cross
2021-04-01 7:33 ` Eli Zaretskii
2021-04-01 8:57 ` Tim Cross
2021-04-01 9:17 ` tomas
2021-04-01 9:56 ` Daniel Brooks
2021-04-01 9:36 ` Gregor Zattler
2021-04-01 10:11 ` Andreas Schwab
2021-04-01 7:25 ` Eli Zaretskii
2021-04-01 8:34 ` Tim Cross
2021-04-01 9:00 ` Eli Zaretskii
2021-04-01 10:56 ` Stefan Kangas
2021-04-01 13:03 ` Eli Zaretskii
2021-04-01 13:32 ` Stefan Kangas
2021-04-01 13:02 ` Eli Zaretskii
2021-04-01 13:01 ` Eli Zaretskii
2021-04-01 13:03 ` Stefan Monnier
2021-04-01 13:07 ` Eli Zaretskii
2021-04-01 13:32 ` Stefan Kangas
2021-04-01 13:36 ` Eli Zaretskii
2021-04-01 15:32 ` Stefan Monnier
2021-04-01 15:37 ` Eli Zaretskii
2021-04-01 16:05 ` extraclean and admin/grammars [was Re: Git master head build failure?] Glenn Morris
2021-04-01 16:09 ` Lars Ingebrigtsen
2021-04-01 16:19 ` Lars Ingebrigtsen
2021-04-02 4:19 ` Tim Cross
2021-04-02 5:58 ` Eli Zaretskii
2021-04-02 13:41 ` Lars Ingebrigtsen
2021-04-02 13:58 ` Eli Zaretskii
2021-04-01 18:31 ` Eli Zaretskii
2021-04-02 13:40 ` Lars Ingebrigtsen
2021-04-02 13:57 ` Eli Zaretskii
2021-04-03 13:30 ` Lars Ingebrigtsen
2021-04-03 14:15 ` Eli Zaretskii
2021-04-03 22:36 ` chad
2021-04-04 7:20 ` Eli Zaretskii
2021-04-03 23:52 ` Tim Cross
2021-04-04 7:39 ` Eli Zaretskii [this message]
2021-04-04 19:44 ` Lars Ingebrigtsen
2021-04-01 17:15 ` Stefan Monnier
2021-04-01 19:56 ` Eli Zaretskii
2021-04-01 20:13 ` Stefan Monnier
2021-04-03 7:58 ` Eli Zaretskii
2021-04-13 2:20 ` Stefan Monnier
2021-04-13 11:51 ` Eli Zaretskii
2021-04-13 12:19 ` Eli Zaretskii
2021-04-13 13:01 ` Stefan Monnier
2021-04-13 12:59 ` Stefan Monnier
2021-04-13 14:03 ` Eli Zaretskii
2021-04-01 18:29 ` Eli Zaretskii
2021-04-04 16:28 ` Glenn Morris
2021-04-04 17:12 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838s5yebwx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@gnu.org \
--cc=theophilusx@gmail.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://git.savannah.gnu.org/cgit/emacs.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).