From: Jason Rumney <jasonr@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Bootstrap fails on w32
Date: Sun, 22 May 2005 22:29:33 +0100 [thread overview]
Message-ID: <uy8a7t0ea.fsf@jasonrumney.net> (raw)
In-Reply-To: <4290EDA8.7020401@student.lu.se> (Lennart Borgman's message of "Sun, 22 May 2005 22:38:00 +0200")
Lennart Borgman <lennart.borgman.073@student.lu.se> writes:
>>Did you run "cvs update -kb" in the emacs/nt directory, as recommended
>>by the INSTALL file in there?
>>
>>
>>
> Eh..., no. I totally forgot that. Thanks.
>
> BTW why is this not done in the repository?
Because the files are not binary, so we lose most of CVS's
functionality by labelling them as binary. I generally keep two copies
of the nt directory checked out. One checked out with -kb for
compiling with, and one checked out normally for checking in any
changes I make, or doing diffs etc.
next prev parent reply other threads:[~2005-05-22 21:29 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-21 22:09 Bootstrap fails on w32 Lennart Borgman
2005-05-22 3:22 ` Eli Zaretskii
2005-05-22 10:06 ` Lennart Borgman
2005-05-22 20:34 ` Eli Zaretskii
2005-05-22 20:07 ` Jason Rumney
2005-05-22 20:38 ` Lennart Borgman
2005-05-22 20:52 ` Michael Cadilhac
2005-05-22 21:29 ` Jason Rumney [this message]
2005-05-22 21:52 ` Juanma Barranquero
2005-05-22 22:13 ` Jason Rumney
2005-05-22 22:27 ` Juanma Barranquero
2005-05-22 22:34 ` Juanma Barranquero
2005-05-23 0:26 ` Adrian Aichner
2005-05-23 7:50 ` Juanma Barranquero
2005-05-23 8:36 ` Andreas Schwab
2005-05-23 3:59 ` Eli Zaretskii
2005-05-23 8:06 ` Juanma Barranquero
2005-05-24 0:23 ` Eli Zaretskii
2005-05-23 23:50 ` David Kastrup
2005-05-24 3:38 ` Eli Zaretskii
2005-05-24 7:03 ` Juanma Barranquero
2005-05-24 8:43 ` David Kastrup
2005-05-24 8:58 ` Juanma Barranquero
2005-05-24 19:06 ` Eli Zaretskii
2005-05-24 19:37 ` Lennart Borgman
2005-05-25 3:55 ` Eli Zaretskii
2005-05-22 21:54 ` David Kastrup
2005-05-22 22:17 ` Jason Rumney
2005-05-22 22:30 ` David Kastrup
2005-05-22 23:45 ` Jason Rumney
2005-05-23 0:15 ` David Kastrup
2005-05-23 3:49 ` Eli Zaretskii
2005-05-23 8:46 ` David Kastrup
2005-05-23 10:56 ` Juanma Barranquero
2005-05-31 18:10 ` Juanma Barranquero
2005-05-31 23:02 ` Lennart Borgman
2005-05-24 0:31 ` Eli Zaretskii
2005-05-23 3:51 ` Eli Zaretskii
2005-05-23 13:26 ` Werner LEMBERG
2005-05-25 1:00 ` Kenichi Handa
2005-05-25 3:45 ` Werner LEMBERG
2005-05-25 7:08 ` Jason Rumney
2005-05-25 8:30 ` Werner LEMBERG
2005-05-25 8:45 ` Andreas Schwab
2005-05-25 18:23 ` Eli Zaretskii
2005-05-25 19:36 ` Daniel Brockman
2005-05-26 5:37 ` Werner LEMBERG
2005-05-22 22:34 ` Lennart Borgman
2005-05-24 12:55 ` Lennart Borgman
2005-05-24 19:16 ` Eli Zaretskii
2005-05-23 4:03 ` Eli Zaretskii
2005-05-23 8:08 ` Juanma Barranquero
2005-05-24 0:24 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2005-05-23 9:40 LENNART BORGMAN
2005-05-24 8:33 martin rudalics
2005-05-24 9:47 ` Jason Rumney
2005-05-27 9:25 ` martin rudalics
2005-06-02 8:51 ` jasonr
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uy8a7t0ea.fsf@jasonrumney.net \
--to=jasonr@gnu.org \
--cc=emacs-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).