From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: mail@justinbogner.com
Cc: emacs-devel@gnu.org
Subject: Re: your vc-hg.el change
Date: Tue, 25 Nov 2008 16:25:26 +0900 [thread overview]
Message-ID: <871vx0jmhl.fsf@xemacs.org> (raw)
In-Reply-To: <87k5as334q.fsf@justinbogner.com>
mail@justinbogner.com writes:
> "Stephen J. Turnbull" <stephen@xemacs.org> writes:
> > For bzr, it is mildly important *not* to change the status quo. Emacs
> > developers especially will be hurt if bzr doesn't allow pointing to a
> > user-installed bzr, as every recent bzr release has improved
> > performance.
> >
>
> Wouldn't the user's PATH point to the bzr they like?
The bzr I like depends on which project I am working on at the
moment. Ditto the darcs. That's one reason why I like git best of
all. ;-)
Specifically, since Emacs has not yet implemented bzr, I really don't
give two shakes of a lamb's tail whether I trash my Emacs repo, or
even whether I can access it on any given day. In the event I write a
patch I'll be doing it against CVS. So I can update my bzr for Emacs
nightly. I don't plan to do that for my Mailman repos as they
occasionally contain code that may not exist anywhere else; I stick to
whatever Gentoo considers stable.
> I find it unlikely that they would be able to reasonably use it
> otherwise...
It's a bit fragile, but making that variable buffer-local DTRTs. YMMV.
next prev parent reply other threads:[~2008-11-25 7:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200811221752.mAMHqCqK020038@mothra.ics.uci.edu>
2008-11-24 7:38 ` your vc-hg.el change Glenn Morris
2008-11-24 9:31 ` Dan Nicolaescu
2008-11-24 17:18 ` Glenn Morris
2008-11-24 18:02 ` Chong Yidong
2008-11-24 15:52 ` Chong Yidong
2008-11-24 17:15 ` Glenn Morris
2008-11-24 18:01 ` Chong Yidong
2008-11-24 18:19 ` Glenn Morris
2008-11-25 1:59 ` Stephen J. Turnbull
2008-11-25 3:17 ` mail
2008-11-25 7:25 ` Stephen J. Turnbull [this message]
2009-01-12 10:36 Norman Gray
2010-11-17 14:36 ` 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=871vx0jmhl.fsf@xemacs.org \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=mail@justinbogner.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).