unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Angelo Graziosi <angelo.graziosi@alice.it>, Emacs <emacs-devel@gnu.org>
Subject: Re: BZR error!
Date: Mon, 04 Jan 2010 21:01:37 -0500	[thread overview]
Message-ID: <jwvk4vx2tum.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <m3y6kdkccu.fsf@hase.home> (Andreas Schwab's message of "Mon, 04 Jan 2010 18:29:21 +0100")

>>> May be related to the fact that trunk is a symlink now.  As a workaround
>>> you can use the emacs-23 branch instead.
>> Can someone confirm that this is the culprit?
> It's common that http servers ignore symlinks for security reasons.
> It's not even listed in <http://bzr.savannah.gnu.org/r/emacs>.

OK, I reverted this change, so there's no more `emacs-23' branch and
trunk is not a symlink any more.


        Stefan




  reply	other threads:[~2010-01-05  2:01 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-04 10:01 BZR error! Angelo Graziosi
2010-01-04 12:30 ` Tassilo Horn
2010-01-04 12:43   ` Juanma Barranquero
2010-01-04 13:24     ` Óscar Fuentes
2010-01-04 13:30     ` Tassilo Horn
2010-01-04 18:29       ` Eli Zaretskii
2010-01-04 20:28         ` Andreas Schwab
2010-01-04 20:39         ` Stefan Monnier
2010-01-05  4:03           ` Eli Zaretskii
2010-01-05  6:16             ` Óscar Fuentes
2010-01-05 15:10               ` Stefan Monnier
2010-01-05 15:49                 ` Andreas Schwab
2010-01-05 16:37                   ` Stefan Monnier
2010-01-05 17:16                     ` Andreas Schwab
2010-01-05 17:36                       ` Óscar Fuentes
2010-01-04 14:32 ` Andreas Schwab
2010-01-04 14:45   ` Angelo Graziosi
2010-01-04 14:49     ` Andreas Schwab
2010-01-04 15:05       ` Angelo Graziosi
2010-01-04 15:27         ` Tassilo Horn
2010-01-04 15:33           ` Werner LEMBERG
2010-01-04 15:41             ` Miles Bader
2010-01-04 15:46             ` Juanma Barranquero
2010-01-04 15:56               ` Werner LEMBERG
2010-01-04 15:59                 ` Juanma Barranquero
2010-01-04 16:05               ` Miles Bader
2010-01-04 16:08                 ` Juanma Barranquero
2010-01-05  3:31             ` Richard Stallman
2010-01-04 15:27         ` Juanma Barranquero
2010-01-04 15:48           ` Angelo Graziosi
2010-01-04 15:51             ` Juanma Barranquero
2010-01-04 16:58         ` Óscar Fuentes
2010-01-05  3:31       ` Richard Stallman
2010-01-05 19:29         ` Eli Zaretskii
2010-01-04 15:33   ` Sven Joachim
2010-01-04 17:07   ` Stefan Monnier
2010-01-04 17:29     ` Andreas Schwab
2010-01-05  2:01       ` Stefan Monnier [this message]
2010-01-04 21:39 ` Tom Tromey
2010-01-06  3:24   ` Karl Fogel
2010-01-06  4:26     ` Tom Tromey
  -- strict thread matches above, loose matches on Subject: below --
2010-01-04 13:50 Angelo Graziosi
2010-01-04 20:29 ` Christian Lynbech

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=jwvk4vx2tum.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=angelo.graziosi@alice.it \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.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).