unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 12001@debbugs.gnu.org
Subject: bug#12001: 24.1.50; vc-diff always talks to CVS repository
Date: Tue, 21 Aug 2012 17:22:48 -0400	[thread overview]
Message-ID: <E1T3vuS-0004yx-Lc@fencepost.gnu.org> (raw)
In-Reply-To: <5vtxvw529e.fsf@fencepost.gnu.org> (message from Glenn Morris on Mon, 20 Aug 2012 23:53:49 -0400)

In fact, the problem is happening with bzr using the Emacs sources.

I don't know why I wrote CVS in the subject -- habit took over, I
suppose.  I have a vague memory of seeing it a few weeks ago with CVS
in editing gnu.org web pages, but this bug report is with bzr.

    Maybe rms has somehow ended up with a lightweight checkout, or a stacked
    branch, or some other non-standard form of bzr repository that does not
    actually keep all the data locally.

    What does `bzr info' report in the local copy?

Repository checkout (format: 2a)
Location:
  repository checkout root: .
        checkout of branch: bzr+ssh://rms@bzr.savannah.gnu.org/emacs/trunk/
         shared repository: /home/rms/emacs-bzr

I set up my repository as recommended in BzrQuickStartForEmacsDevs.  I
chose this because it is the simplest, both to set up and to use in
practice, and also the most similar to CVS.

vc-diff should support it correctly.

--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org  www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
  Use Ekiga or an ordinary phone call






  reply	other threads:[~2012-08-21 21:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20 18:45 bug#12001: 24.1.50; vc-diff always talks to CVS repository Richard Stallman
2012-07-20 19:10 ` Andreas Schwab
2012-07-21  2:43   ` Richard Stallman
2012-07-21  8:01     ` Andreas Schwab
2012-08-19 22:29       ` Richard Stallman
2012-08-20  7:25         ` Andreas Schwab
2012-08-21  2:20           ` Richard Stallman
2012-08-21  2:52             ` Eli Zaretskii
2012-08-21  3:53               ` Glenn Morris
2012-08-21 21:22                 ` Richard Stallman [this message]
2012-08-22  2:56                   ` Eli Zaretskii
2012-08-22  3:13                     ` Glenn Morris
2012-08-22 16:26                       ` Eli Zaretskii
2012-08-22 16:33                         ` Glenn Morris
2012-08-23  2:49                       ` Richard Stallman
2012-08-23  7:09                         ` Glenn Morris
2012-08-23  7:14                           ` Glenn Morris
2012-08-23  7:16                             ` Glenn Morris
2012-08-23  8:18                           ` Paul Eggert
2012-08-24  2:17                             ` Richard Stallman
2012-08-24  4:06                               ` Paul Eggert

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=E1T3vuS-0004yx-Lc@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=12001@debbugs.gnu.org \
    --cc=rgm@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).