unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Lilja <mindcooler@gmail.com>
To: emacs-devel@gnu.org
Subject: Worth doing fresh checkout of emacs 22 branch
Date: Tue, 15 May 2007 14:34:10 +0200	[thread overview]
Message-ID: <f2c9ba$al5$1@sea.gmane.org> (raw)

Hello!

Right now I'm running GNU Emacs 22.0.99.1 (i386-mingw-nt5.1.2600) of 
2007-04-24

I noticed my laptop was using a lot older version so I'm trying to 
decide if I should copy the binaries from my main computer or build 
again using a fresh checkout. I know the emacs release is Really Close 
Now<tm>, but it's been a few weeks since the last prerelease and I was 
thinking that maybe fixes have gone in that could be worth having. What 
do you say? It takes less than ten minutes for me to do full bootstrap 
so that time spent is not an issue.
Here's my build script for the emacs 22 branch btw:
#!/bin/bash
export CVS_RSH="ssh"
touch ~/.cvspass
cvs -z3 -d:pserver:anonymous@cvs.savannah.gnu.org:/sources/emacs co -r 
EMACS_22_BASE emacs
rm ~/.cvspass
cd emacs/nt/
./configure.bat --with-gcc --no-cygwin --no-debug
mingw32-make bootstrap --jobs=2 XMFLAGS="--jobs=2"
mingw32-make install

Is that correct if I want to build the latest sources of what is going 
to be Emacs 22?

- Eric

             reply	other threads:[~2007-05-15 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 12:34 Eric Lilja [this message]
2007-05-15 20:39 ` Worth doing fresh checkout of emacs 22 branch Eli Zaretskii
2007-05-15 20:43   ` Eric Lilja

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='f2c9ba$al5$1@sea.gmane.org' \
    --to=mindcooler@gmail.com \
    --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).