From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Diff between Branches
Date: Sat, 31 Oct 2009 14:44:47 +0100 [thread overview]
Message-ID: <20091031134447.GA22646@thorin> (raw)
In-Reply-To: <20091031123657.GA29323@pina.cat>
On Sat, Oct 31, 2009 at 12:36:57PM +0000, Carles Pina i Estany wrote:
>
> Hi,
>
> I'm novice with Bazaar.
> I would like to diff between gettext branch and trunk. I did:
>
> bzr branch http://bzr.savannah.gnu.org/r/grub/people/robertmh/gettext/
The gettext branch was based on an old trunk, I've just regenerated it,
try branching again.
> bzr diff -r branch:http://bzr.savannah.gnu.org/r/ub/trunk/grub
>
> But I have some unexpected results like adding files and removing files
> that I would not expect:
Is this what you wanted?
bzr diff -r ancestor:bzr+ssh://bzr.savannah.gnu.org/grub/trunk/grub
Btw, if you're just trying to resync, it's better if you use bzr for that,
e.g.:
$ bzr pull bzr+ssh://bzr.savannah.gnu.org/grub/trunk/grub
bzr: ERROR: These branches have diverged. Use the missing command to see how.
Use the merge command to reconcile them.
$ bzr merge bzr+ssh://bzr.savannah.gnu.org/grub/trunk/grub
[...]
Text conflict in conf/common.rmk
Text conflict in kern/misc.c
Text conflict in util/grub-mkconfig_lib.in
Text conflict in util/grub.d/00_header.in
Text conflict in util/grub.d/10_linux.in
5 conflicts encountered.
<some manual work with conf/common.rmk and conf/common.rmk.*>
$ bzr resolve conf/common.rmk
<repeat untill all conflicts are resolved, then commit>
After this is done, you can push to /people/<your-dir>/gettext or so.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
prev parent reply other threads:[~2009-10-31 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 12:36 Diff between Branches Carles Pina i Estany
2009-10-31 13:26 ` Colin Watson
2009-10-31 13:45 ` Robert Millan
2009-10-31 14:23 ` Colin Watson
2009-10-31 13:44 ` Robert Millan [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091031134447.GA22646@thorin \
--to=rmh@aybabtu.com \
--cc=grub-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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.