unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Karl Fogel <kfogel@red-bean.com>
Cc: Tim Penhey <tim@penhey.net>, Barry Warsaw <barry@python.org>,
	Emacs Development <emacs-devel@gnu.org>
Subject: vc-dir header for bzr (was: Re: [PATCH] vc-bzr.el: avoid stomping files across hardlink branches.)
Date: Mon, 1 Dec 2008 12:10:34 -0800 (PST)	[thread overview]
Message-ID: <200812012010.mB1KAYsT016435@mothra.ics.uci.edu> (raw)
In-Reply-To: <874p2h36n4.fsf@red-bean.com> (Karl Fogel's message of "Sat, 08 Nov 2008 22:44:31 -0500")

Since you seem to be interested in VC with bzr, can you please look at
the following issue too?

In vc-dir it is possible to add custom headers for each VC backend. 
Currently for bzr only a single one is used "Parent branch". 
But it seems that "bzr info" offers more information that can be useful:

$ bzr info
Standalone tree (format: pack-0.92)
Location:
  branch root: FOOBAR

Related branches:
    push branch: FOO
  parent branch: BAR


Is there anything else that could be added to the headers here?
Thanks.
                --dan




  parent reply	other threads:[~2008-12-01 20:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200810292207.58558.tim@penhey.net>
2008-11-09  3:44 ` [PATCH] vc-bzr.el: avoid stomping files across hardlink branches Karl Fogel
2008-11-09  4:33   ` Miles Bader
2008-11-09  4:44     ` Karl Fogel
2008-11-09 15:03   ` Stefan Monnier
2008-11-10  2:29     ` Tim Penhey
2008-11-10  3:31       ` Stefan Monnier
2008-11-10 22:39         ` Karl Fogel
2008-11-11  2:47           ` Stefan Monnier
2008-11-29 19:05             ` Karl Fogel
2008-12-01 20:10   ` Dan Nicolaescu [this message]
2008-12-01 20:30     ` vc-dir header for bzr Karl Fogel

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=200812012010.mB1KAYsT016435@mothra.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=barry@python.org \
    --cc=emacs-devel@gnu.org \
    --cc=kfogel@red-bean.com \
    --cc=tim@penhey.net \
    /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).