From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: emacs build broken?
Date: Fri, 29 Jan 2010 17:00:17 +1100 [thread overview]
Message-ID: <871vh9mowe.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: 5aed60c6-0e9d-4b63-9c28-44c63e91b5bd@k5g2000pra.googlegroups.com
rustom <rustompmody@gmail.com> writes:
> On Jan 29, 9:50 am, rustom <rustompm...@gmail.com> wrote:
>> On Jan 28, 1:50 pm, José A. Romero L. <escherdra...@gmail.com> wrote:
>> > (...)
>>
>> > Didn't emacs move to bazaar for good? (http://www.emacswiki.org/emacs/
>> > BzrForEmacsDevs)
>> (...)
>> If we stuck around with things like cvs a bit longer the other part of
>> the acronym will also become true (GNU = Generally Not Used)
>> He also (seehttp://johnbokma.com/mexit/2008/04/16/)
>
> Ok so
>
> http://bzr.savannah.gnu.org/lh/emacs/trunk/files
>
> seems broken
>
> I wonder which is worse and antediluvian cvs or a broken bzr?
I've pulled down the emacs bzr repository both today and yesterday
on different machines (i.e. full/heave bzr checkout) and it works fine.
Note that the URL for the bzr checkout is
http://bzr.savannah.gnu.org/r/emacs/trunk/
while
http://bzr.savannah.gnu.org/lh/emacs/trunk/
is the log head for browsing the repository, which may well be broken.
(the difference is /r/ in one and /lh/ in the other).
On both systems, emacs built without errors. The initial heavy checkout
does take a while i.e. 20+ minutes on a fairly fast conneciton. However,
after that, updates are quite fast.
Tim
--
tcross (at) rapttech dot com dot au
next prev parent reply other threads:[~2010-01-29 6:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 7:44 emacs build broken? rustom
2010-01-28 7:57 ` rustom
2010-01-28 8:50 ` José A. Romero L.
2010-01-29 4:50 ` rustom
2010-01-29 5:44 ` rustom
2010-01-29 6:00 ` Tim X [this message]
2010-01-29 9:43 ` José A. Romero L.
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=871vh9mowe.fsf@lion.rapttech.com.au \
--to=timx@nospam.dev.null \
--cc=help-gnu-emacs@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 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.