From: Eli Zaretskii <eliz@gnu.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: sean.sieger@gmail.com, emacs-devel@gnu.org
Subject: Re: emacs-20101122 windows binaries
Date: Tue, 23 Nov 2010 21:22:11 +0200 [thread overview]
Message-ID: <83k4k3976k.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTimDimU=PHvz5H40Zym28y-mPVc=rxecAWAbO_bz@mail.gmail.com>
> From: Lennart Borgman <lennart.borgman@gmail.com>
> Date: Tue, 23 Nov 2010 19:39:41 +0100
> Cc: Sean Sieger <sean.sieger@gmail.com>, emacs-devel@gnu.org
>
> >> - Releases should or should not include debug info?
> >
> > It is IMO slightly better to ship the release without debug info.
>
> Why not ship to versions of the release binaries, with and without debug info?
Because it's pointless. If we want to give users release binaries
with debug info, we should just ship such a binary, period.
next prev parent reply other threads:[~2010-11-23 19:22 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 [this message]
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
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=83k4k3976k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--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.