all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@gnu.org>
To: Manuel Giraud <manuel.giraud@univ-nantes.fr>
Cc: emacs-devel@gnu.org
Subject: Re: machine specific patch (OpenBSD)
Date: Wed, 13 Jul 2011 10:40:06 -0400	[thread overview]
Message-ID: <yxqwrfmgs6x.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <871uxucls5.fsf@univ-nantes.fr> (Manuel Giraud's message of "Wed,  13 Jul 2011 16:12:10 +0200")

Manuel Giraud <manuel.giraud@univ-nantes.fr> writes:

> Hi,
>
> I'd like to know if machine specific patches are something that can go
> in the repo before officially releasing emacs 24 ? In my case, I'd like
> to push some of the patches for OpenBSD^1. For instance, the following
> patch avoid emacs 24 to freeze at start under X:
>
>
> --8<---------------cut here---------------start------------->8---
> === modified file 'src/s/openbsd.h'
> --- src/s/openbsd.h     2011-01-15 23:16:57 +0000
> +++ src/s/openbsd.h     2011-07-13 13:28:30 +0000
> @@ -3,3 +3,4 @@
>  /* The same as NetBSD.  Note there are differences in configure.  */
>  #include "netbsd.h"
>  
> +#define BROKEN_SIGIO
> --8<---------------cut here---------------end--------------->8---
>
> Best regards,
>
> 1: http://www.openbsd.org/cgi-bin/cvsweb/ports/editors/emacs23/patches/

How about showing the patches and not a link to them ?
But before doing that please update the patches.  A quick look at one of
them showed that it defining macros that are no longer in use in the
tree.



  reply	other threads:[~2011-07-13 14:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13 14:12 machine specific patch (OpenBSD) Manuel Giraud
2011-07-13 14:40 ` Dan Nicolaescu [this message]
2011-07-13 15:22   ` Manuel Giraud
2011-07-13 23:00     ` Paul Eggert
2011-07-19  9:52       ` Manuel Giraud
2011-07-19 17:44         ` Paul Eggert
2011-07-20 11:31           ` Manuel Giraud

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=yxqwrfmgs6x.fsf@fencepost.gnu.org \
    --to=dann@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=manuel.giraud@univ-nantes.fr \
    /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.