all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Eric M. Ludlam" <eric@siege-engine.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Chong Yidong <cyd@stupidchicken.com>, Eric Ludlam <zappo@gnu.org>,
	5483@debbugs.gnu.org
Subject: bug#5483: 23.1.91; EDE : proj-automake : files in subdirectories have no `ede-current-project'
Date: Mon, 01 Feb 2010 14:29:27 -0500	[thread overview]
Message-ID: <4B672B97.5080901@siege-engine.com> (raw)
In-Reply-To: <jwv4om1dl1e.fsf-monnier+emacs@gnu.org>



On 02/01/2010 10:40 AM, Stefan Monnier wrote:
>> Well, my lisp ability is rather limited, but I'll launch a message on the
>> mailing list, with the information I've gathered.
>
>> Question is, where should any development go into? CEDET cvs or Emacs' bzr?
>
> It's probably better for it to go into the Emacs bzr, because it's a lot
> easier for Eric to merge from our repository than the other way around
> (for legal reasons on his side).
> Eric, what do you think?

If Someone other than me makes a change set that is complete, then this 
is true.  If I need to be involved then it would need to be done in 
CEDET cvs since my last release ended 2 days ago, and I need to get it 
refreshed.

Eric






  reply	other threads:[~2010-02-01 19:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <873a1qxans.fsf@stupidchicken.com>
     [not found] ` <4B62176A.7050609@siege-engine.com>
2010-01-31 16:48   ` bug#5483: 23.1.91; EDE : proj-automake : files in subdirectories have no `ede-current-project' Lluís
2010-01-31 22:02     ` Eric M. Ludlam
2010-02-01 15:40     ` Stefan Monnier
2010-02-01 19:29       ` Eric M. Ludlam [this message]
2020-11-19  3:02     ` Stefan Kangas
2020-11-20 17:50       ` Lluís
2020-11-20 18:05         ` Stefan Kangas
2021-01-01 18:56           ` Stefan Kangas
2010-01-26 21:41 Lluís

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=4B672B97.5080901@siege-engine.com \
    --to=eric@siege-engine.com \
    --cc=5483@debbugs.gnu.org \
    --cc=cyd@stupidchicken.com \
    --cc=monnier@iro.umontreal.ca \
    --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.