From: Miles Bader <snogglethorpe@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: New speedbar version
Date: Mon, 3 Oct 2005 12:07:38 +0900 [thread overview]
Message-ID: <fc339e4a051002200761a6202c@mail.gmail.com> (raw)
In-Reply-To: <877jcwj7st.fsf-monnier+emacs@gnu.org>
2005/10/2, Stefan Monnier <monnier@iro.umontreal.ca>:
> > Unfortunately, checking in the new version of Speedbar (which has been
> > undergoing development in its own tree for two years) was itself one
> > of the items needed for the release. See, for example,
>
> > http://lists.gnu.org/archive/html/emacs-devel/2005-05/msg00202.html
>
> BTW, could whoever worked on this speedbar.el thingy install on a branch the
> "original" upstream version, so that in the future we will be able to
> trivially extract the local changes we've made (or, equivalently, to easily
> install a newer upstream release o n that branch and then ask CVS to do
> (most of) the merge for us)?
Anyway, as a general rule: _never_ just "check in" new versions of
upstream files. _Always_ merge them. If that seems annoying then the
first step is to track down the history you need to do such a merge
(and hopefully, as Stefan suggests, do some preparation so that the
next merge is easier).
-Miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2005-10-03 3:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-01 0:13 New speedbar version Chong Yidong
2005-10-01 20:48 ` Nick Roberts
2005-10-04 14:19 ` Chong Yidong
2005-10-05 7:49 ` Nick Roberts
2005-10-07 13:07 ` Romain Francoise
2005-10-08 8:48 ` Ralf Angeli
2005-10-02 14:48 ` Stefan Monnier
2005-10-03 3:07 ` Miles Bader [this message]
2005-10-03 15:35 ` Richard M. Stallman
-- strict thread matches above, loose matches on Subject: below --
2005-09-30 14:47 Chong Yidong
2005-09-30 17:07 ` Bill Wohler
2005-09-30 17:55 ` Romain Francoise
2005-09-30 23:11 ` Nick Roberts
2005-10-01 15:10 ` Richard M. Stallman
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=fc339e4a051002200761a6202c@mail.gmail.com \
--to=snogglethorpe@gmail.com \
--cc=miles@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.