From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Ralf Angeli <angeli@caeruleus.net>
Cc: emacs-devel@gnu.org
Subject: Re: RefTeX Merge
Date: Wed, 26 Sep 2012 16:59:17 +0900 [thread overview]
Message-ID: <87ehlpmcyy.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <87haqlwbya.fsf@caeruleus.net>
Ralf Angeli writes:
> I tried to get some information about `brz join' but there does not
> seem to be much available. And given the problems with the command
> discussed on emacs-devel it looks a bit dangerous.
DVCS means never having to say you're sorry. And I mean *never*.[1]
Remember, all dangerous operations can be conducted on a copy of the
repo. All it costs is a small amount of disk space for a short period
of time.
> I'm not yet sure if it would be the right tool for the job because
> we want to do a merge of files existing in both repositories
This isn't possible in bzr, because bzr tracks "file containers", and
there is no provision for identifying "containers" from repositories
without a common ancestor. No matter how you slice it, you're going
to get an add-add conflict unless you delete one copy or the other
first. I can see how to do this in git, but it wouldn't be pleasant
(both ugly and painstaking, but you'd probably end up with a usable
history).
Why do you want to do that, anyway? What are these files that exist
in both repos? Do they really have independent lines of development
in both repos? Or is one a slightly tweaked copy of the other?
> and the description of `bzr join' talks about combining a tree with
> a subtree.
Yup. Seems to me that is what you *should* want to do. If this falls
afoul of RMS's preference for "sufficient number of files" in a
subtree, fix that *after* the join by bzr-move'ing the files into the
appropriate place.
> What would be the steps involved?
I can't give specific advice without answers to the questions above.
Footnotes:
[1] Well, until you push. ;-)
next prev parent reply other threads:[~2012-09-26 7:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 18:10 RefTeX Merge Ralf Angeli
2012-09-23 18:39 ` Paul Eggert
2012-09-24 6:13 ` Chong Yidong
2012-09-24 20:44 ` Ralf Angeli
2012-09-24 23:32 ` Richard Stallman
2012-09-25 6:30 ` Tassilo Horn
2012-09-26 6:11 ` Ralf Angeli
2012-09-26 7:09 ` Tassilo Horn
2012-09-26 7:59 ` Stephen J. Turnbull [this message]
2012-09-26 13:20 ` Stefan Monnier
2012-09-26 10:20 ` Chong Yidong
2012-09-26 13:24 ` Subdirectories in `lisp' Stefan Monnier
2012-09-30 20:46 ` RefTeX Merge Ralf Angeli
2012-09-23 18:48 ` Glenn Morris
2012-09-23 18:58 ` Glenn Morris
2012-09-23 19:09 ` Glenn Morris
2012-09-24 1:42 ` Glenn Morris
2012-09-24 1:50 ` Glenn Morris
2012-09-24 21:02 ` Ralf Angeli
2012-10-16 7:39 ` Tassilo Horn
2012-11-01 14:05 ` Ralf Angeli
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=87ehlpmcyy.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=angeli@caeruleus.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.