From: "Davis Herring" <herring@lanl.gov>
To: "Andreas Röhler" <andreas.roehler@online.de>
Cc: emacs-devel@gnu.org
Subject: Re: Change to bzr build instructions
Date: Sun, 27 Mar 2011 11:54:53 -0700 (PDT) [thread overview]
Message-ID: <55382.130.55.132.57.1301252093.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <4D8C9C76.5070600@online.de>
>> [ .. ] Why would bzr insist
>> people remember to use bzr mv instead of the shell command mv?
>
> Does it?
>
> When copying whole bzr-directories with shell didn't notice a loss. (?)
This is for moves within (not of) working copies that one intends to commit.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2011-03-27 18:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 0:24 Change to bzr build instructions Glenn Morris
2011-03-21 0:46 ` Glenn Morris
2011-03-21 16:06 ` Jim Meyering
2011-03-21 22:33 ` Stefan Monnier
2011-03-22 3:31 ` Glenn Morris
2011-03-22 5:42 ` Stefan Monnier
2011-03-22 7:16 ` Glenn Morris
2011-03-22 8:08 ` Jim Meyering
2011-03-22 9:32 ` Andreas Schwab
2011-03-23 3:15 ` Glenn Morris
2011-03-22 11:36 ` Andreas Röhler
2011-03-22 13:09 ` Harald Hanche-Olsen
2011-03-22 18:37 ` Glenn Morris
2011-03-25 9:54 ` Eli Zaretskii
2011-03-25 10:04 ` David Kastrup
2011-03-25 10:18 ` Eli Zaretskii
2011-03-25 11:44 ` Leo
2011-03-25 13:07 ` David Kastrup
2011-03-25 13:13 ` Eli Zaretskii
2011-03-25 13:52 ` David Kastrup
2011-03-25 16:02 ` Eli Zaretskii
2011-03-25 13:45 ` Andreas Röhler
2011-03-27 18:54 ` Davis Herring [this message]
2011-03-25 14:37 ` Ted Zlatanov
2011-03-25 15:03 ` David Kastrup
2011-03-25 15:16 ` Ted Zlatanov
2011-03-25 15:32 ` David Kastrup
2011-03-25 16:08 ` Eli Zaretskii
2011-03-25 19:55 ` Stefan Monnier
2011-03-28 1:11 ` Miles Bader
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=55382.130.55.132.57.1301252093.squirrel@webmail.lanl.gov \
--to=herring@lanl.gov \
--cc=andreas.roehler@online.de \
--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).