From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 19989@debbugs.gnu.org, ilya@math.berkeley.edu
Subject: bug#19989: 25.0.50; Build instructions on Windows
Date: Fri, 06 Mar 2015 21:27:04 +0200 [thread overview]
Message-ID: <83sidilyev.fsf@gnu.org> (raw)
In-Reply-To: <54F9F7A4.5000205@gmx.at>
> Date: Fri, 06 Mar 2015 19:53:24 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: ilya@math.berkeley.edu, 19989@debbugs.gnu.org
>
> > The only rule I follow (religiously, btw) is not to overwrite a DLL
> > with an older one, judging by its time stamp. I didn't find any other
> > issues.
>
> When I am busy resolving dependencies it's easy to sidestep this rule at
> least once.
It depends on which tools you use to unpack. If the tools allow you
to say "do not override with older files", the probability of errors
is greatly reduced.
> You have a well maintained code base and much superior knowledge.
> Starting from scratch is not comparable to that.
I, too, started from scratch at some point ;-)
next prev parent reply other threads:[~2015-03-06 19:27 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 16:34 bug#19989: 25.0.50; Build instructions on Windows Ilya Zakharevich
2015-03-03 17:00 ` Eli Zaretskii
2015-03-03 17:21 ` Eli Zaretskii
2015-03-03 20:30 ` Ilya Zakharevich
2015-03-04 3:42 ` Eli Zaretskii
2015-03-05 21:18 ` Ilya Zakharevich
2015-03-06 8:29 ` Eli Zaretskii
2015-03-06 9:21 ` martin rudalics
2015-03-06 9:59 ` Ilya Zakharevich
2015-03-06 11:16 ` Eli Zaretskii
2015-03-07 1:44 ` Ilya Zakharevich
2015-03-07 9:11 ` Eli Zaretskii
2015-03-08 6:22 ` Ilya Zakharevich
2015-08-15 8:03 ` Eli Zaretskii
2015-08-15 11:22 ` Dani Moncayo
2015-08-15 11:38 ` Dani Moncayo
2015-08-15 12:10 ` Eli Zaretskii
2015-08-15 12:09 ` Eli Zaretskii
2015-08-15 12:24 ` Dani Moncayo
2015-08-15 12:26 ` Eli Zaretskii
2015-08-15 13:39 ` Dani Moncayo
2015-03-06 10:28 ` Eli Zaretskii
2015-03-06 14:13 ` Óscar Fuentes
2015-03-06 14:14 ` Óscar Fuentes
2015-03-06 14:40 ` Eli Zaretskii
2015-03-07 1:47 ` Ilya Zakharevich
2015-03-07 2:04 ` Óscar Fuentes
2015-03-07 9:19 ` Eli Zaretskii
2015-03-06 18:53 ` martin rudalics
2015-03-06 19:27 ` Eli Zaretskii [this message]
2015-03-07 9:40 ` martin rudalics
2015-03-07 10:04 ` Eli Zaretskii
2015-03-07 10:28 ` martin rudalics
2015-03-08 6:07 ` Ilya Zakharevich
2015-03-08 10:04 ` martin rudalics
2015-03-08 16:07 ` Ilya Zakharevich
2015-03-06 9:46 ` Ilya Zakharevich
2015-03-06 10:33 ` Eli Zaretskii
2015-03-07 1:37 ` Ilya Zakharevich
2015-03-06 10:08 ` Eli Zaretskii
2015-03-07 1:35 ` Ilya Zakharevich
2015-03-07 9:04 ` Eli Zaretskii
2015-03-08 6:14 ` Ilya Zakharevich
2015-03-08 15:46 ` Eli Zaretskii
2015-03-08 16:04 ` Ilya Zakharevich
2015-03-08 16:59 ` Eli Zaretskii
2015-03-03 21:15 ` Ilya Zakharevich
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=83sidilyev.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19989@debbugs.gnu.org \
--cc=ilya@math.berkeley.edu \
--cc=rudalics@gmx.at \
/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.