unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Karl Fogel <kfogel@red-bean.com>
Cc: cschol2112@googlemail.com, lennart.borgman@gmail.com,
	emacs-devel@gnu.org, schwab@linux-m68k.org, svenjoac@gmx.de,
	jearl@notengoamigos.org
Subject: Re: [beuc@gnu.org: Re: [Savannah-hackers-public] bzr move from	sftp:// to bzr+ssh:// [done]]
Date: Mon, 11 Oct 2010 22:44:42 +0200	[thread overview]
Message-ID: <83y6a4larp.fsf@gnu.org> (raw)
In-Reply-To: <87fwwcwk5h.fsf@kslab.red-bean.com>

> From: Karl Fogel <kfogel@red-bean.com>
> Cc: Jason Earl <jearl@notengoamigos.org>,  cschol2112@googlemail.com,  schwab@linux-m68k.org,  lennart.borgman@gmail.com,  svenjoac@gmx.de,  emacs-devel@gnu.org
> Date: Mon, 11 Oct 2010 16:26:34 -0400
> 
> >> bzr pull --remember bzr://bzr.savannah.gnu.org/emacs/trunk/
> >> 
> >> will do the right thing on the next bzr pull.
> >
> >Is "bzr pull" the right thing to do with a bound branch?  That's what
> >many people here use, so if it isn't TRT, the above could cause
> >trouble.
> 
> I don't know, but I have a bound branch and I always use 'bzr up'.
> It seems to work fine.

Me too.  That's why I asked.



  reply	other threads:[~2010-10-11 20:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-10 12:39 [beuc@gnu.org: Re: [Savannah-hackers-public] bzr move from sftp:// to bzr+ssh:// [done]] Eli Zaretskii
2010-10-10 12:56 ` Lars Magne Ingebrigtsen
2010-10-10 13:47   ` Andreas Schwab
2010-10-10 13:49   ` Eli Zaretskii
2010-10-10 14:01     ` Lars Magne Ingebrigtsen
2010-10-10 14:30       ` Eli Zaretskii
2010-10-10 16:42         ` David Kastrup
2010-10-10 17:07           ` Karl Fogel
2010-10-11  4:55       ` Richard Stallman
2010-10-10 12:57 ` Andreas Schwab
2010-10-10 14:03 ` B Smith-Mannschott
2010-10-10 14:36   ` Eli Zaretskii
2010-10-10 14:56     ` Eli Zaretskii
2010-10-10 16:07   ` Andreas Schwab
2010-10-10 17:01 ` Christoph
2010-10-11  7:01   ` Sven Joachim
2010-10-11 11:54     ` Lennart Borgman
2010-10-11 13:05       ` Andreas Schwab
2010-10-11 14:06         ` Lennart Borgman
2010-10-11 15:33           ` Jason Earl
2010-10-11 19:05             ` Eli Zaretskii
2010-10-11 20:26               ` Karl Fogel
2010-10-11 20:44                 ` Eli Zaretskii [this message]
2010-10-11 22:18                   ` Jason Earl
2010-10-12  3:21               ` Stephen J. Turnbull
2010-10-11 15:46           ` Óscar Fuentes
2010-10-13  0:27           ` Stefan Monnier
2010-10-14  0:42     ` Christoph
  -- strict thread matches above, loose matches on Subject: below --
2010-10-10 13:03 Richard Stallman
2010-10-18 21:07 ` Alan Mackenzie
2010-10-19  4:00   ` Eli Zaretskii

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=83y6a4larp.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cschol2112@googlemail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jearl@notengoamigos.org \
    --cc=kfogel@red-bean.com \
    --cc=lennart.borgman@gmail.com \
    --cc=schwab@linux-m68k.org \
    --cc=svenjoac@gmx.de \
    /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).