unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: emacs-devel@gnu.org
Subject: Re: Switching to bzr: what remains to be done?
Date: Thu, 18 Dec 2008 09:00:00 +0100	[thread overview]
Message-ID: <87r645hq0v.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <873agm9zmh.fsf@canonical.com> (Karl Fogel's message of "Wed, 17 Dec 2008 17:59:50 -0500")

Karl Fogel <karl.fogel@canonical.com> writes:

Hi Karl,

> Progress report on the 4 bugs we've highlighted as blockers:
>
>    1) 'bzr log' only takes a single file argument
>        (https://bugs.launchpad.net/bzr/+bug/211852)
>
>        Developer vila has commented in the bug, but there is no
>        timeline to fix it.  I'm asking vila whether he plans to.
>
>    2) 'bzr log SUBDIR' doesn't show all changes under SUBDIR
>        (https://bugs.edge.launchpad.net/bzr/+bug/97715)
>
>        Developer abentley has commented that this is hard (at least,
>        that's how I interpret "This isn't really practical without
>        changes to the inventory format.")  Is this one definitely a
>        blocker for us, or just a nice-to-have?

I don't have any bzr repository checked out currently, so I couldn't
test my assertion.  But reading the docs of bzr-1.10 it seems to me that
`bzr diff' only accepts files as arguments (no directories), too.

Maybe that could make syncing parts that also have an external
repository difficult.  One candidate suffering from that could be
org-mode, which resides at lisp/org/.

Bye,
Tassilo
-- 
A child of five could understand this! Fetch me a child of five!




  reply	other threads:[~2008-12-18  8:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-08 18:59 Switching to bzr: what remains to be done? Karl Fogel
2008-12-08 19:29 ` Dan Nicolaescu
2008-12-08 19:51   ` Karl Fogel
2008-12-08 21:44   ` Stefan Monnier
2008-12-11 22:43     ` Karl Fogel
2008-12-08 19:54 ` Stefan Monnier
2008-12-09  0:59   ` Stephen J. Turnbull
     [not found]     ` <878wqqf8gr.fsf@notengoamigos.org>
2008-12-09  3:16       ` Stefan Monnier
     [not found]   ` <87hc5ef9mf.fsf@notengoamigos.org>
2008-12-09  3:32     ` Stefan Monnier
2008-12-09  9:33       ` Andreas Schwab
     [not found]       ` <87zlj5dvij.fsf@notengoamigos.org>
2008-12-09 19:55         ` Stefan Monnier
2008-12-09  2:45 ` Dan Nicolaescu
2008-12-11 20:23   ` Karl Fogel
2008-12-17 22:59     ` Karl Fogel
2008-12-18  8:00       ` Tassilo Horn [this message]
2008-12-18 16:28         ` Karl Fogel
2008-12-19  8:22           ` Tassilo Horn
2008-12-19  8:29         ` Giorgos Keramidas
2008-12-18 20:26       ` Dan Nicolaescu
2009-01-05  0:00       ` Tom Tromey
2009-01-05  2:14         ` Stefan Monnier
2009-01-05  2:42           ` Tom Tromey
2009-01-05  4:04             ` Stefan Monnier
2009-01-06  0:01             ` Richard M Stallman
  -- strict thread matches above, loose matches on Subject: below --
2008-12-08 16:32 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=87r645hq0v.fsf@thinkpad.tsdh.de \
    --to=tassilo@member.fsf.org \
    --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).