unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: nickrob@snap.net.nz (Nick Roberts)
Cc: Dmitry Dzhus <dima@sphinx.net.ru>, emacs-devel@gnu.org
Subject: Re: Emacs and the Google Summer of Code
Date: Fri, 24 Apr 2009 09:20:04 -0400	[thread overview]
Message-ID: <jwvr5ziyyu3.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <18929.26723.199888.664316@totara.tehura.co.nz> (Nick Roberts's message of "Fri, 24 Apr 2009 19:21:07 +1200")

>> > I know that RMS does not like this idea, as he thinks that all focus
>> > will shift to the new branch, but I'm not sure if that's true and
>> > there are drawbacks in not having one.  Debian seem to manage with
>> > both a testing and unstable distribution.
>> This is a completely different issue.  We're talking about a branch for
>> a particular feature.  We're not talking about opening "a new trunk".
> I probably wasn't very clear but that's exactly what I was talking about.
> Yidong's post also seems to suggest that this might be possible.  Creating
> a sparate branch for one Emacs mode is probably not worthwhile as experience
> from GDB tells me that very few people would check that branch out.

As long as we're in pretest, I don't really want to encourage people to
try development code.  But AFAIK, there's still a fair bit of
development to be done on that GDB/MI thing before it needs testing, so
I think it's not an issue.


        Stefan




      reply	other threads:[~2009-04-24 13:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23  7:15 Emacs and the Google Summer of Code Nick Roberts
2009-04-23  8:42 ` Miles Bader
2009-04-23 12:33 ` Chong Yidong
2009-04-23 14:35 ` Stefan Monnier
2009-04-24  7:21   ` Nick Roberts
2009-04-24 13:20     ` Stefan Monnier [this message]

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=jwvr5ziyyu3.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dima@sphinx.net.ru \
    --cc=emacs-devel@gnu.org \
    --cc=nickrob@snap.net.nz \
    /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).