all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Engster <deng@randomsample.de>
To: Chong Yidong <cyd@gnu.org>
Cc: "Eric M. Ludlam" <zappo@gnu.org>, Lluís <xscript@gmx.net>,
	emacs-devel@gnu.org
Subject: Re: Merging CEDET
Date: Sat, 28 Jul 2012 18:23:18 +0200	[thread overview]
Message-ID: <876297n9c9.fsf@engster.org> (raw)
In-Reply-To: <87r4rvrjew.fsf@gnu.org> (Chong Yidong's message of "Sat, 28 Jul 2012 23:32:07 +0800")

Chong Yidong writes:
> David Engster <deng@randomsample.de> writes:
>
>> As I've already written some time ago, I've started to write a special
>> package for merging Emacs<->CEDET.  The most important goal is to keep
>> the granularity of commits in both repositories. 
>
> Any progress on this?  It would be a shame for the CEDET merge to miss
> the 24.2 merge window.  Or are you still waiting for more input?

It would help to know more about that window. Like, when it ends. :-)

There's one thing I need help with, and that's the final step of pushing
commits into Emacs trunk. I will prepare a branch 'to-emacs' in CEDET
where commits can be cleanly applied to Emacs, but I need someone to
double check and do the final push to Emacs. After that grammar file
disaster, I'm not willing to step into this mine field alone.

-David



  parent reply	other threads:[~2012-07-28 16:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-02  7:47 Merging CEDET Chong Yidong
     [not found] ` <4FCB6B01.8020600@siege-engine.com>
2012-06-03 18:00   ` David Engster
2012-06-03 21:51     ` Lluís
2012-06-04 13:34     ` Stefan Monnier
2012-07-28 15:32     ` Chong Yidong
2012-07-28 15:38       ` Emacs 24.2 merge window (was: Merging CEDET) Bastien
2012-07-28 16:23       ` David Engster [this message]
2012-07-29  3:21         ` Merging CEDET Chong Yidong

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=876297n9c9.fsf@engster.org \
    --to=deng@randomsample.de \
    --cc=cyd@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=xscript@gmx.net \
    --cc=zappo@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 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.