From: Eli Zaretskii <eliz@gnu.org>
To: "Stephen J. Turnbull" <turnbull@sk.tsukuba.ac.jp>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: splitting ChangeLogs
Date: Thu, 07 Apr 2011 06:03:21 +0300 [thread overview]
Message-ID: <837hb6vk3q.fsf@gnu.org> (raw)
In-Reply-To: <8739lurj78.fsf@uwakimon.sk.tsukuba.ac.jp>
> From: "Stephen J. Turnbull" <turnbull@sk.tsukuba.ac.jp>
> Cc: lekktu@gmail.com,
> emacs-devel@gnu.org
> Date: Thu, 07 Apr 2011 09:36:27 +0900
>
> Eli Zaretskii writes:
>
> > So what am I missing?
>
> The logs and diffs.
>
> If before for splitting ChangeLog, bzr log ChangeLog shows N
> revisions, after either of the procedures shown, one of ChangeLog and
> ChangeLog.11 has 1 revision, and the other has N+1. bzr diff does
> nothing useful with the newly added file. With a hypothetical bzr cp,
> both would have N+1, and bzr diff would work on both.
I think I see the light now. You are saying that with "bzr cp", the
DAG will still be (almost) the same, except that "bzr diff" and other
commands will simply act _as_if_ the new ChangeLog had the same
history as the old one. Right?
next prev parent reply other threads:[~2011-04-07 3:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 1:49 splitting ChangeLogs Juanma Barranquero
2011-04-06 3:00 ` Eli Zaretskii
2011-04-06 3:24 ` Juanma Barranquero
2011-04-06 9:19 ` Eli Zaretskii
2011-04-06 11:18 ` Juanma Barranquero
2011-04-06 3:43 ` Stephen J. Turnbull
2011-04-06 9:20 ` Eli Zaretskii
2011-04-06 9:39 ` Stephen J. Turnbull
2011-04-06 12:23 ` Eli Zaretskii
2011-04-07 0:36 ` Stephen J. Turnbull
2011-04-07 3:03 ` Eli Zaretskii [this message]
2011-04-07 5:10 ` Stephen J. Turnbull
2011-04-06 4:01 ` Glenn Morris
2011-04-06 4:58 ` Stephen J. Turnbull
2011-04-06 5:05 ` Leo
2011-04-06 9:11 ` Eli Zaretskii
2011-04-06 9:14 ` Eli Zaretskii
2011-04-06 15:21 ` Stefan Monnier
[not found] ` <83hbabv1ol.fsf@gnu.org>
2011-04-06 16:53 ` Stefan Monnier
2011-04-06 18:08 ` Eli Zaretskii
2011-04-06 11:15 ` Juanma Barranquero
2011-04-06 17:22 ` Glenn Morris
2011-04-06 15:19 ` Stefan Monnier
2011-04-06 15:21 ` Juanma Barranquero
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=837hb6vk3q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=turnbull@sk.tsukuba.ac.jp \
/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).