unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Strange message from "bzr pull"
Date: Tue, 29 Dec 2009 05:30:30 -0500	[thread overview]
Message-ID: <E1NPZLS-0002GL-F0@fencepost.gnu.org> (raw)
In-Reply-To: <f7ccd24b0912290218j7a5a51d7g37e4513cf1dc8e17@mail.gmail.com> (message from Juanma Barranquero on Tue, 29 Dec 2009 11:18:40 +0100)

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Tue, 29 Dec 2009 11:18:40 +0100
> Cc: emacs-devel@gnu.org
> 
> >   M  lisp/ChangeLog
> >   M  lisp/vc-bzr.el
> >  All changes applied successfully.
> >  Now on revision 99211.
> >
> > In CVS, the "M" marker meant that I have local uncommitted changes.
> > But I don't have such changes here, at least not consciously.  So what
> > does this message mean, and how do I dig into the reasons for it (if
> > there are any)?
> 
> It just means that pull brought changes for these files.

So it's like "P" in CVS.

What surprised me was that I never saw such messages from "bzr pull"
when the bzr repository was just the result of CVS conversion by
Andreas, as opposed to a writable repository it is now.  Why didn't I
see such messages back then?




  reply	other threads:[~2009-12-29 10:30 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29  7:43 Strange message from "bzr pull" Eli Zaretskii
2009-12-29 10:18 ` Juanma Barranquero
2009-12-29 10:30   ` Eli Zaretskii [this message]
2009-12-29 12:40     ` Juanma Barranquero
2009-12-29 16:24       ` Eli Zaretskii
2009-12-29 17:00         ` Karl Fogel
2009-12-29 18:10           ` Eli Zaretskii
2009-12-29 18:13             ` Juanma Barranquero
2009-12-29 18:34               ` Eli Zaretskii
2009-12-29 19:28                 ` Óscar Fuentes
2009-12-29 19:51                   ` Karl Fogel
2009-12-29 20:04                     ` Óscar Fuentes
2009-12-29 20:15                       ` Karl Fogel
2009-12-29 20:29                       ` Eli Zaretskii
2009-12-29 23:32                         ` Óscar Fuentes
2009-12-30  4:16                           ` Eli Zaretskii
2009-12-30  5:15                             ` Óscar Fuentes
2009-12-31  9:39                       ` Stephen J. Turnbull
2009-12-29 20:16                   ` Eli Zaretskii
2009-12-29 23:14                     ` Óscar Fuentes
2009-12-30  4:21                       ` Eli Zaretskii
2009-12-30  4:28                         ` Miles Bader
2009-12-30  5:26                         ` Óscar Fuentes
2009-12-29 18:44             ` Karl Fogel
2009-12-29 19:01               ` Eli Zaretskii
2009-12-29 19:09                 ` Karl Fogel
2009-12-29 20:09                   ` Eli Zaretskii
2009-12-30  7:02                     ` Eli Zaretskii
2009-12-30 12:19                       ` Juanma Barranquero
2009-12-30 15:05                         ` Eli Zaretskii
2009-12-30 15:19                           ` Juanma Barranquero
2009-12-31 19:36                           ` Karl Fogel
2009-12-31 20:49                             ` Juanma Barranquero
2009-12-29 21:37                 ` Stefan Monnier
2009-12-31  9:43                   ` Stephen J. Turnbull
2009-12-29 18:02       ` Eli Zaretskii
2009-12-29 18:12         ` Juanma Barranquero

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=E1NPZLS-0002GL-F0@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    /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).