From: "Eric M. Ludlam" <eric@siege-engine.com>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: State of the CEDET merge
Date: Sat, 12 Mar 2011 08:15:45 -0500 [thread overview]
Message-ID: <4D7B7201.6050208@siege-engine.com> (raw)
In-Reply-To: <87lj0kr7y3.fsf@fencepost.gnu.org>
On 03/12/2011 04:42 AM, David Kastrup wrote:
> Lluís<xscript@gmx.net> writes:
>
>> David Kastrup writes:
>>> Sounds like having to track two separately moving targets.
>>
>> In fact, I'm only tracking changes introduced in Emacs. But not those
>> introduced after my last merge for a specific file (these will have to
>> be manually re-checked).
>>
>> Changes in the cedet trunk should be automatically merged when I merge
>> the branch.
>>
>>
>>> Any idea how to make the respective developers aware of the problem
>>> and move in a more synchronized fashion, so as to decrease the speed
>>> with which the task you have focused on grows?
>>
>> There's no easy solution.
>>
>> On one hand, files in Emacs where introduced with modification wrt the
>> cedet CVS, so some of them are hard to track.
>>
>> On the other hand, people won't be able to contribute all the fixes into
>> cedet instead of emacs and expect emacs tu pull from cedet; not until I
>> finish the file-rename branch.
>>
>> All this, added with my lack of elisp skill, knowledge on cedet
>> internals and knowledge on what has been changed and why, make the task
>> a tough one.
>
> Let's assume that you get the task completed in the manner you envision
> and you are working on right now, and the merge and synch happens as
> planned.
>
> Will that leave Cedet and Emacs in a state where future synchronizations
> of Cedet to Emacs will be possible in a semi-automatic manner, like Gnus
> is synchronized frequently right now?
>
> Or will it mean that every future synchronization will require just as
> much effort as your current work?
>
> In short: if you manage to catch up with your target, will it be
> reasonably easy to keep it from running off again?
>
I'm not that familiar with bzr, but the idea is that once this
conversion is done, merges could be automated on some way, except for
conflicts. My dream is some sort of cron job that merges from Emacs
back into a CEDET integration branch, and also from the CEDET trunk into
the integration branch, and warns when a merge fails. When Emacs wants
to sync back, the merge would be quite simple from the integration
branch at any time. Periodically, someone could merge the Emacs
integration branch into CEDET trunk.
The challenge is just finding someone with the right skills and time to
help out.
Eric
next prev parent reply other threads:[~2011-03-12 13:15 UTC|newest]
Thread overview: 130+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 5:34 Emacs 23.3 released Chong Yidong
2011-03-10 8:58 ` Bastien
2011-03-10 16:07 ` Stefan Monnier
2011-03-10 16:22 ` David Kastrup
2011-03-10 16:54 ` Chong Yidong
2011-03-10 17:54 ` David Kastrup
2011-03-10 18:00 ` Lennart Borgman
2011-03-10 19:17 ` State of the CEDET merge (was: Emacs 23.3 released) David Engster
2011-03-11 14:29 ` State of the CEDET merge Lluís
2011-03-11 14:45 ` David Kastrup
2011-03-11 15:48 ` Lluís
2011-03-12 9:42 ` David Kastrup
2011-03-12 13:15 ` Eric M. Ludlam [this message]
2011-03-12 20:49 ` Stefan Monnier
2011-03-13 14:13 ` Ted Zlatanov
2011-03-14 19:55 ` Lluís
2011-03-14 20:39 ` Lennart Borgman
2011-03-14 22:28 ` Lluís
2011-03-13 15:13 ` David Engster
2011-03-14 20:08 ` Lluís
2011-03-15 1:33 ` Stefan Monnier
2011-03-16 14:03 ` Lluís
2011-03-16 15:24 ` Stefan Monnier
2011-03-16 15:30 ` David Kastrup
2011-03-16 20:23 ` Lluís
2011-03-18 17:43 ` Eli Zaretskii
2011-03-18 17:51 ` Eli Zaretskii
2011-07-24 8:14 ` David Kastrup
2011-07-24 10:01 ` David Engster
2011-07-24 13:11 ` David Kastrup
2011-07-27 2:46 ` Chong Yidong
2011-07-27 6:25 ` David Kastrup
2011-07-27 7:21 ` David Engster
2011-07-27 7:39 ` David Kastrup
2011-07-27 8:06 ` Andreas Röhler
2011-07-27 8:24 ` David Kastrup
2011-07-27 16:14 ` Compiled files without sources???? Richard Stallman
2011-07-27 17:57 ` David Kastrup
2011-07-28 5:53 ` Richard Stallman
2011-07-28 10:02 ` Paul Eggert
2011-07-28 23:00 ` Richard Stallman
2011-07-28 23:28 ` Paul Eggert
2011-07-29 14:32 ` Milan
2011-07-29 22:33 ` Chong Yidong
2011-07-30 2:12 ` Chong Yidong
2011-07-30 4:36 ` Richard Stallman
2011-07-30 20:33 ` Chong Yidong
2011-07-30 23:20 ` Thien-Thi Nguyen
2011-07-31 4:46 ` Tim Cross
2011-07-31 11:03 ` David Kastrup
2011-07-31 13:29 ` Tim Cross
2011-07-31 17:45 ` Andreas Röhler
2011-07-31 17:55 ` Stephen J. Turnbull
2011-07-31 18:06 ` Lars Ingebrigtsen
2011-07-31 20:06 ` Stephen J. Turnbull
2011-07-31 21:47 ` David Engster
2011-07-31 22:36 ` David Kastrup
2011-07-31 23:15 ` David Engster
2011-08-01 0:14 ` Chong Yidong
2011-07-31 23:10 ` Tim Cross
2011-08-01 12:33 ` Stephen J. Turnbull
2011-08-01 13:14 ` David Kastrup
2011-08-01 14:37 ` Stephen J. Turnbull
2011-08-01 14:42 ` Thien-Thi Nguyen
2011-08-02 0:13 ` Richard Stallman
2011-08-02 7:10 ` David Kastrup
2011-08-03 4:17 ` Richard Stallman
2011-08-02 0:13 ` Letting the users off the hook Richard Stallman
2011-08-03 4:16 ` Richard Stallman
2011-08-03 6:50 ` Stephen J. Turnbull
2011-08-03 19:18 ` Richard Stallman
2011-07-31 23:56 ` Compiled files without sources???? Richard Stallman
2011-07-31 16:19 ` Richard Stallman
2011-07-31 17:04 ` Chong Yidong
2011-07-31 23:56 ` Richard Stallman
2011-08-01 3:08 ` Chong Yidong
2011-08-01 21:28 ` Replacing tarballs on-the-fly (was: Re: Compiled files without sources????) Ulrich Mueller
2011-08-02 16:09 ` Replacing tarballs on-the-fly Chong Yidong
2011-08-02 17:43 ` Ulrich Mueller
2011-08-03 4:17 ` Richard Stallman
2011-08-03 20:31 ` Chong Yidong
2011-08-02 0:13 ` Compiled files without sources???? Richard Stallman
2011-08-02 15:56 ` Chong Yidong
2011-08-03 4:16 ` Richard Stallman
2011-07-30 4:35 ` Richard Stallman
2011-07-29 16:25 ` Evgeny M. Zubok
2011-07-29 16:37 ` David Kastrup
2011-07-29 23:40 ` Richard Stallman
2011-07-30 12:56 ` Evgeny M. Zubok
2011-07-30 13:25 ` David Kastrup
2011-07-30 20:55 ` Chong Yidong
2011-07-31 16:19 ` Richard Stallman
2011-03-10 16:45 ` Emacs 23.3 released Juanma Barranquero
2011-03-11 4:26 ` Stefan Monnier
2011-03-11 4:42 ` Juanma Barranquero
2011-03-11 9:44 ` Andreas Schwab
2011-03-11 20:18 ` Stefan Monnier
2011-03-11 23:03 ` Andreas Schwab
2011-03-12 0:03 ` Juanma Barranquero
2011-03-12 1:38 ` Stefan Monnier
2011-03-10 19:21 ` Thierry Volpiatto
2011-03-11 4:20 ` Stefan Monnier
2011-03-11 7:14 ` Thierry Volpiatto
2011-03-12 3:35 ` Stefan Monnier
2011-03-12 12:23 ` Juanma Barranquero
2011-03-14 14:10 ` Stefan Monnier
2011-03-14 14:52 ` Juanma Barranquero
2011-03-14 15:51 ` Lexbind (was: Emacs 23.3 released) Stefan Monnier
2011-03-17 1:59 ` Juanma Barranquero
2011-03-17 10:28 ` Eli Zaretskii
2011-03-17 12:22 ` Juanma Barranquero
2011-03-17 15:13 ` Juanma Barranquero
2011-03-17 16:07 ` Eli Zaretskii
2011-03-17 18:06 ` Juanma Barranquero
2011-03-17 19:24 ` Eli Zaretskii
2011-03-17 19:46 ` Juanma Barranquero
2011-03-19 0:54 ` Juanma Barranquero
2011-03-19 8:35 ` Eli Zaretskii
2011-03-19 9:28 ` Juanma Barranquero
2011-03-17 20:01 ` Lexbind Stefan Monnier
2011-03-17 22:07 ` Lexbind Wojciech Meyer
2011-03-17 23:29 ` Lexbind Juanma Barranquero
2011-03-18 7:39 ` Lexbind joakim
2011-03-10 19:27 ` Emacs 23.3 released Mike Mattie
2011-03-10 19:56 ` Glenn Morris
2011-03-11 8:45 ` Eli Zaretskii
2011-03-11 16:56 ` Chong Yidong
2011-03-11 20:19 ` Stefan Monnier
2011-03-10 18:57 ` Chong Yidong
2011-03-12 9:28 ` updating web manuals [Re: " Jim Meyering
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=4D7B7201.6050208@siege-engine.com \
--to=eric@siege-engine.com \
--cc=dak@gnu.org \
--cc=emacs-devel@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).