From: Lennart Borgman <lennart.borgman@gmail.com>
To: Jason Rumney <jasonr@gnu.org>
Cc: Sean Sieger <sean.sieger@gmail.com>, emacs-devel@gnu.org
Subject: Re: emacs-20101122 windows binaries
Date: Wed, 24 Nov 2010 00:06:42 +0100 [thread overview]
Message-ID: <AANLkTimzdB8pdSj8nqqXiFihkJbbyTSYzHtPsb+GR8HE@mail.gmail.com> (raw)
In-Reply-To: <874ob7tzlr.fsf@home.jasonrumney.net>
On Wed, Nov 24, 2010 at 12:00 AM, Jason Rumney <jasonr@gnu.org> wrote:
> Sean Sieger <sean.sieger@gmail.com> writes:
>
>> Jason Rumney <jasonr@gnu.org> writes:
>>
>> I guess no debug info has been included (probably not a good idea for
>> snapshots).
>>
>> My bad:
>>
>> - Snapshots should or should not include debug info?
>> - Pretests should or should not include debug info?
>
> Snapshots and Pretests are primarily for testing, so including debug
> info is essential.
>
>> - Releases should or should not include debug info?
>
> In my experience, users complain (still in 2010) about the size of the
> binary if it changes drastically between releases. So shipping without
> debug info avoids such complaints at the expense that bugs are harder to
> debug (but most users that would be willing to debug for you will be
> using the snapshots or willing to build from source anyway).
I offer the same question as I did before: Is there any advantage of
shipping both binaries with debug info and without it? (In separate
downloads, of course.)
next prev parent reply other threads:[~2010-11-23 23:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 22:11 emacs-20101122 windows binaries Sean Sieger
2010-11-23 2:20 ` Eric Lilja
2010-11-23 14:06 ` Eric Lilja
2010-11-23 15:02 ` Jason Rumney
2010-11-23 16:01 ` Sean Sieger
2010-11-23 16:18 ` Stefan Monnier
2010-11-23 18:39 ` Eli Zaretskii
2010-11-23 18:39 ` Lennart Borgman
2010-11-23 19:22 ` Eli Zaretskii
2010-11-23 19:28 ` Lennart Borgman
2010-11-23 19:52 ` Eli Zaretskii
2010-11-23 19:56 ` Lennart Borgman
2010-11-23 20:50 ` Eli Zaretskii
[not found] ` <AANLkTimwK2svWBCGocR0zT5=qDsn3Z6=kUK=Wz0VqYYk@mail.gmail.com>
[not found] ` <83d3pv92az.fsf@gnu.org>
2010-11-23 21:10 ` Lennart Borgman
2010-11-23 21:18 ` Eli Zaretskii
2010-11-23 21:33 ` Lennart Borgman
2010-11-24 2:11 ` Stephen J. Turnbull
2010-11-24 3:58 ` Eli Zaretskii
2010-11-23 23:00 ` Jason Rumney
2010-11-23 23:06 ` Lennart Borgman [this message]
2010-11-24 4:06 ` Eli Zaretskii
2010-11-24 14:34 ` Stefan Monnier
2010-11-25 23:43 ` Sean Sieger
2010-11-23 23:42 ` Drew Adams
2010-11-24 2:15 ` Stephen J. Turnbull
2010-11-24 5:14 ` Drew Adams
2010-11-24 9:56 ` Stephen J. Turnbull
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=AANLkTimzdB8pdSj8nqqXiFihkJbbyTSYzHtPsb+GR8HE@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jasonr@gnu.org \
--cc=sean.sieger@gmail.com \
/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.