From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: VMS support
Date: Thu, 24 Jul 2008 22:40:18 +0200 [thread overview]
Message-ID: <87od4n2ez1.fsf@ambire.localdomain> (raw)
In-Reply-To: <jwvmyk712cl.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 24 Jul 2008 16:00:03 -0400")
() Stefan Monnier <monnier@IRO.UMontreal.CA>
() Thu, 24 Jul 2008 16:00:03 -0400
I can assure you that it's not the same if your code is in
the trunk vs if your code is on some other branch: when I
edit the the C code and see an "#ifdef VMS" I'll try to pay
attention to that code, even if I can't test that my change
doesn't break it. If it's not in the trunk, I won't see
the #ifdef and you'll have to deal with the breakage.
Whoever does porting work has to deal w/ the breakage, anyway,
regardless of the intention/care of others. I appreciate your
saying you would take care, but the care you take is not the
only factor.
But that's enough from me on this topic.
thi
next prev parent reply other threads:[~2008-07-24 20:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87iquzmcxm.fsf@stupidchicken.com>
[not found] ` <87d4l76ntu.fsf@ambire.localdomain>
2008-07-21 19:52 ` VMS support Chong Yidong
2008-07-23 10:27 ` Thien-Thi Nguyen
2008-07-23 20:05 ` Stefan Monnier
2008-07-24 7:44 ` Thien-Thi Nguyen
2008-07-24 13:59 ` Stefan Monnier
2008-07-24 16:55 ` Dan Nicolaescu
2008-07-24 19:58 ` Stefan Monnier
2008-07-27 18:41 ` Dan Nicolaescu
2008-07-27 18:48 ` Stefan Monnier
2008-07-27 19:06 ` Dan Nicolaescu
2008-07-27 19:31 ` Stefan Monnier
2008-07-27 19:51 ` Dan Nicolaescu
2008-07-27 20:44 ` Stefan Monnier
2008-07-27 21:41 ` Dan Nicolaescu
2008-07-28 9:15 ` Thien-Thi Nguyen
2008-07-24 17:34 ` Thien-Thi Nguyen
2008-07-24 20:00 ` Stefan Monnier
2008-07-24 20:40 ` Thien-Thi Nguyen [this message]
2008-07-24 2:23 ` Richard M Stallman
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=87od4n2ez1.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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).