From: Ali Bahrami <ali_gnu@emvision.com>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: 1191@emacsbugs.donarmstrong.com
Subject: bug#1191: How to contribute back changes for Emacs on Solaris
Date: Thu, 11 Dec 2008 11:21:42 -0700 [thread overview]
Message-ID: <49415A36.7000309@emvision.com> (raw)
In-Reply-To: <200812111814.mBBIEpki000573@mothra.ics.uci.edu>
Dan Nicolaescu wrote:
> Ben made the changes you requested:
>
> commit 7086ee26381fdcc645d12c3177ee0be072dd82ef
> Author: Ben Elliston <bje@gnu.org>
> Date: Thu Dec 11 15:31:45 2008 +1100
>
> * config.guess (i86pc:SunOS:5.*:*, i86xen:SunOS:5.*:*): The full
> path to /usr/bin/echo is necessary to work around the shell
> builtins for echo that do not handle newlines. From Ali
> Bahrami.
>
> and those are checked in the emacs CVS now. Is that what you had in
> mind? If yes, please verify that things work for you now.
>
> --dan
Oh, great! I didn't know, sorry.
I will pull a fresh workspace, test it this afternoon, and
report back.
- Ali
next prev parent reply other threads:[~2008-12-11 18:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200812120309.mBC392kD002742@mothra.ics.uci.edu>
2008-10-17 3:44 ` bug#1191: How to contribute back changes for Emacs on Solaris Ali Bahrami
2008-10-17 6:22 ` Dan Nicolaescu
2008-10-17 16:27 ` Ali Bahrami
2008-10-17 23:52 ` Dan Nicolaescu
2008-10-19 3:18 ` Ali Bahrami
2008-10-20 22:29 ` Dan Nicolaescu
2008-10-23 6:45 ` Ali Bahrami
2008-10-23 16:23 ` Ali Bahrami
2008-10-23 19:35 ` Dan Nicolaescu
2008-10-23 22:51 ` Ali Bahrami
2008-10-23 23:06 ` Dan Nicolaescu
2008-10-23 23:21 ` Ali Bahrami
2008-10-24 0:22 ` Dan Nicolaescu
2008-12-11 17:47 ` Dan Nicolaescu
2008-12-11 18:10 ` Ali Bahrami
2008-12-11 18:14 ` Dan Nicolaescu
2008-12-11 18:21 ` Ali Bahrami [this message]
2008-12-12 2:55 ` Ali Bahrami
2008-12-12 3:15 ` bug#1191: marked as done (How to contribute back changes for Emacs on Solaris) Emacs bug Tracking System
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=49415A36.7000309@emvision.com \
--to=ali_gnu@emvision.com \
--cc=1191@emacsbugs.donarmstrong.com \
--cc=dann@ics.uci.edu \
/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).