From: Lennart Borgman <lennart.borgman@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Chad Brown <yandros@mit.edu>,
Emacs-Devel devel <emacs-devel@gnu.org>,
Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: attribute warn_unused_result
Date: Fri, 4 Feb 2011 22:15:36 +0100 [thread overview]
Message-ID: <AANLkTi=PXpUMixq9JO-ya62cRhOZD6+XdexXwu158qdx@mail.gmail.com> (raw)
In-Reply-To: <jwv8vxvwlwo.fsf-monnier+emacs@gnu.org>
On Fri, Feb 4, 2011 at 10:08 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>>> Gnulib's ignore-value module is designed for that. I installed
>>> the following:
>>> ..and it broke the W32 and nextstep builds (at least) again.
>> So what is wrong here, Paul? We have suggested that you make a
>> separate branch for this. Why don't you do that?
>
> AFAIK this last change introduced a bug, just like any other commit can
> (and sometimes does) introduce a bug because some simple omission that's
> easily fixed. I.e. it's very different from the other cases where he
> knew before that his change was going to break the w32 build.
> IIUC people are reacting too strongly to this last problem because it
> just happens to follow the other ones, but really it's a completely
> different case. I myself break the build on a regular basis as well, as
> you all know too well.
Yes, I realized that. A bit too late.
It would have been much easier to realize that with a little bit more
feedback. Mind reading is difficult face to face and even a little bit
more difficult over the net.
> BTW, I'd still like to see someone setup a build farm that can be used
> to keep track of "the last revision that bootstraps", so people who
> don't want to bump into such problems can follow that branch instead
> of trunk.
For me that would indeed be good especially when I need to test some
patch (which happens too often, actually).
next prev parent reply other threads:[~2011-02-04 21:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 14:57 attribute warn_unused_result Eli Zaretskii
2011-02-03 18:53 ` Stefan Monnier
2011-02-03 19:33 ` Paul Eggert
2011-02-03 20:42 ` Chad Brown
2011-02-03 21:30 ` Eli Zaretskii
2011-02-03 21:58 ` Paul Eggert
2011-02-04 0:17 ` Lennart Borgman
2011-02-04 8:18 ` Eli Zaretskii
2011-02-05 16:30 ` Chong Yidong
2011-02-03 21:40 ` Paul Eggert
2011-02-04 8:41 ` Eli Zaretskii
2011-02-04 8:51 ` Paul Eggert
2011-02-04 21:05 ` Stefan Monnier
2011-02-05 8:50 ` Eli Zaretskii
2011-02-03 21:47 ` Lennart Borgman
2011-02-04 21:08 ` Stefan Monnier
2011-02-04 21:15 ` Lennart Borgman [this message]
2011-02-05 9:03 ` Eli Zaretskii
2011-02-05 8:59 ` Eli Zaretskii
2011-02-03 22:08 ` Andy Moreton
2011-02-03 23:00 ` Paul Eggert
2011-02-03 21:16 ` Eli Zaretskii
2011-02-03 21:14 ` Eli Zaretskii
2011-02-04 0:57 ` Paul Eggert
2011-02-04 8:29 ` Eli Zaretskii
2011-02-04 15:50 ` Tom Tromey
2011-02-04 16:38 ` Eli Zaretskii
2011-02-04 17:12 ` Tom Tromey
2011-02-05 0:11 ` Paul Eggert
2011-02-05 9:18 ` Eli Zaretskii
[not found] ` <yyxvd0yxwv1.fsf@fencepost.gnu.org>
2011-02-06 1:34 ` Paul Eggert
2011-02-06 4:07 ` Eli Zaretskii
2011-02-06 7:04 ` Paul Eggert
2011-02-06 10:21 ` Eli Zaretskii
2011-02-06 18:58 ` Paul Eggert
2011-02-06 19:27 ` Eli Zaretskii
2011-02-06 20:11 ` Paul Eggert
2011-02-06 21:26 ` Eli Zaretskii
2011-02-04 21:14 ` Stefan Monnier
2011-02-05 8:57 ` Eli Zaretskii
2011-02-05 16:01 ` Stefan Monnier
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='AANLkTi=PXpUMixq9JO-ya62cRhOZD6+XdexXwu158qdx@mail.gmail.com' \
--to=lennart.borgman@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=yandros@mit.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 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.