From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Chong Yidong <cyd@stupidchicken.com>, zappo@gnu.org, emacs-devel@gnu.org
Subject: Re: Filename problem in CEDET merge
Date: Fri, 28 Aug 2009 11:23:53 -0400 [thread overview]
Message-ID: <jwveiqwj75p.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <838wh4cm0q.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 28 Aug 2009 12:42:29 +0300")
> How about making a subdirectory, in addition to shortening?
> semantic.el --> semantic/semantic.el
> semantic-analyze.el --> semantic/analyze.el
> semantic-analyze-complete.el --> semantic/analyz-complete.el
> semantic-analyze-debug.el --> semantic/analyz-debug.el
That would be OK, as long as we're careful to to add .../semantic to
load-path (otherwise we'd have to be careful to avoid conflicts between
semantic/foo.el and other foo.el packages).
>> Renaming would also have the extremely bad effect of diverging from the
>> CEDET upstream, which I'd like to avoid if possible.
> Maybe the upstream maintainer will agree to rename, in which case we
> don't diverge.
Yes, I think the only acceptable solutions require the upstream version
to apply the same changes.
Stefan
next prev parent reply other threads:[~2009-08-28 15:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 22:50 Filename problem in CEDET merge Chong Yidong
2009-08-28 2:26 ` Eric M. Ludlam
2009-08-28 9:45 ` Eli Zaretskii
2009-08-28 11:16 ` Eric M. Ludlam
2009-08-28 11:27 ` Miles Bader
2009-08-28 13:33 ` Eli Zaretskii
2009-08-28 13:55 ` Eric M. Ludlam
2009-08-28 14:06 ` Eli Zaretskii
2009-08-28 14:58 ` Chong Yidong
2009-08-28 15:23 ` Chong Yidong
2009-08-28 15:46 ` Andreas Schwab
2009-08-28 15:26 ` Stefan Monnier
2009-08-28 9:42 ` Eli Zaretskii
2009-08-28 15:23 ` Stefan Monnier [this message]
2009-08-28 12:14 ` Leo
2009-08-28 13:44 ` Eli Zaretskii
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=jwveiqwj75p.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cyd@stupidchicken.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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 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).