From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: monnier@IRO.UMontreal.CA, emacs-devel@gnu.org
Subject: Re: Merging emacs-23 into trunk
Date: Thu, 11 Nov 2010 21:29:17 +0900 [thread overview]
Message-ID: <87iq04dowy.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <E1PGTBS-0000ei-IQ@fencepost.gnu.org>
Eli Zaretskii writes:
> ??? Which part of design of bzr won't permit me doing the
> following?
Eli, I have no idea how you could possibly think that's an appropriate
question at this point in the thread (and the same goes for several of
your following comments), so I'm going to quit while I'm ahead.
However, in considering how to reply, I did come up with one
suggestion possibly worthy of consideration.
> The issue of whether to have configure in the repository is a separate
> one. If the decision is not to track it, then, of course, all of the
> above is not relevant.
Obviously, configure *is* in the repo. Then you either do something
to prevent the problems I described, or sooner or later they arise.
The obvious thing to do is to run autoconf, then commit configure
along with configure.in.
To keep Glenn happy, maybe the Bazaar guys can come up with a plugin
or a patch that allows you to configure files that should never be
diffed unless you ask for it (like binaries, you just get a stanza in
the diff that says the files differ but the diff itself is omitted
because the file appears in .diffignore or diff.ignore= in
.bzr/config). That likely won't be too hard, because they have to do
something more complex to avoid spewing binary garbage, anyway. So
there is some place where bzr is going, "oh, let's not display the
diff of this file" and suppressing either the diff operation itself or
the output. Quite likely it's a couple of lines to change to add this
feature.
next prev parent reply other threads:[~2010-11-11 12:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 21:30 Merging emacs-23 into trunk Stefan Monnier
2010-11-10 4:34 ` Glenn Morris
2010-11-10 5:44 ` Stephen J. Turnbull
2010-11-10 11:59 ` Eli Zaretskii
2010-11-11 2:28 ` Stephen J. Turnbull
2010-11-11 6:32 ` Eli Zaretskii
2010-11-11 8:39 ` Stephen J. Turnbull
2010-11-11 9:11 ` Eli Zaretskii
2010-11-11 12:29 ` Stephen J. Turnbull [this message]
2010-11-10 9:01 ` Andreas Schwab
2010-11-10 15:38 ` Stefan Monnier
2010-11-10 17:28 ` Glenn Morris
2010-11-10 20:42 ` Glenn Morris
2010-11-10 22:30 ` Chad Brown
2010-11-11 4:02 ` Eli Zaretskii
2010-11-11 5:09 ` Kenichi Handa
2010-11-11 19:55 ` Glenn Morris
2010-11-11 20:01 ` Lennart Borgman
2010-11-11 20:23 ` Óscar Fuentes
2010-11-11 20:49 ` Eli Zaretskii
2010-11-10 12:03 ` Eli Zaretskii
2010-11-10 15:46 ` Stefan Monnier
2010-11-10 17:21 ` Eli Zaretskii
2010-11-10 19:03 ` Stefan Monnier
2010-11-10 19:19 ` Eli Zaretskii
2010-11-10 19:36 ` Óscar Fuentes
2010-11-11 6:26 ` Eli Zaretskii
2010-11-11 17:13 ` Óscar Fuentes
2010-11-11 2:52 ` Stephen J. Turnbull
2010-11-11 6:38 ` Eli Zaretskii
2010-11-10 19:32 ` Óscar Fuentes
2010-11-11 19:57 ` Stefan Monnier
2010-11-11 20:20 ` Óscar Fuentes
[not found] ` <jwvd3qbo3z1.fsf-monnier+emacs@gnu.org>
2010-11-12 16:51 ` Óscar Fuentes
2010-11-12 20:41 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iq04dowy.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.