unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 7560@debbugs.gnu.org
Subject: bug#7560: 24.0.50; 'bzr status' blocking making of GNU Emacs
Date: Mon, 06 Dec 2010 22:54:10 +0200	[thread overview]
Message-ID: <83r5du39n1.fsf@gnu.org> (raw)
In-Reply-To: <0lk4jmk5iy.fsf@fencepost.gnu.org>

> Cc: 7560@debbugs.gnu.org
> From: Glenn Morris <rgm@gnu.org>
> Date: Mon, 06 Dec 2010 15:31:01 -0500
> 
> Eli Zaretskii wrote:
> 
> >> Anyway, to me, the question is: why is the build process running bzr
> >> status at all.
> >
> > Because many file ops, in particular save-buffer, in a versioned
> > directory do that automatically.
> 
> Then I'd ask what the point of having any of that enabled when
> building Emacs is. It cannot do anything useful, only slow the build
> down

Don't we have various VC-related features that make sense even in
batch operations, like special treatment of backups?

So perhaps, if we are annoyed by this during the build, we should turn
it off in the Makefile, not as a general feature of -batch or byte
compilation?





  reply	other threads:[~2010-12-06 20:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-05 16:29 bug#7560: 24.0.50; 'bzr status' blocking making of GNU Emacs Peter Dyballa
2010-12-05 17:04 ` Andreas Schwab
2010-12-05 17:33   ` Eli Zaretskii
2010-12-05 20:09     ` Glenn Morris
2010-12-05 22:38       ` Peter Dyballa
2010-12-06  3:54         ` Eli Zaretskii
2010-12-06  9:38           ` Peter Dyballa
2010-12-06 19:09             ` Eli Zaretskii
2010-12-08 16:29               ` Peter Dyballa
2010-12-08 21:14                 ` Eli Zaretskii
2010-12-06 17:54       ` Glenn Morris
2010-12-06 19:06         ` Eli Zaretskii
2010-12-06 20:31           ` Glenn Morris
2010-12-06 20:54             ` Eli Zaretskii [this message]
2010-12-06 21:46               ` Glenn Morris
2010-12-07  3:21             ` Stefan Monnier

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=83r5du39n1.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=7560@debbugs.gnu.org \
    --cc=rgm@gnu.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://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).