From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: ofv@wanadoo.es, emacs-devel@gnu.org
Subject: Re: log format for vc-bzr
Date: Fri, 08 Jan 2010 14:52:54 +0200 [thread overview]
Message-ID: <831vi0bvx5.fsf@gnu.org> (raw)
In-Reply-To: <f7ccd24b1001080424s7f82d03eibc5b56cfba2e2e9a@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Fri, 8 Jan 2010 13:24:29 +0100
> Cc: ofv@wanadoo.es, emacs-devel@gnu.org
>
> On Fri, Jan 8, 2010 at 13:01, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Thanks, but isn't this in the direction that is opposite of the one
> > for which it was suggested? I though you are supposed to use it
> > _on_the_trunk_, after merging from a branch. But you seem to show it
> > in the other direction, which confuses this issue even more, at least
> > for me.
>
> I don't know what in my message (other than my usual clarity or lack
> of it) makes you think that.
You ran "bzr status" in the trunk, that's why. Sorry.
> > So its effect is similar to that of rebasing?
>
> Humm, no. Leaving aside uncommited changes, conflicts, etc., rebase
> un-applies some commits, updates the branch, and reapplies these
> commits as if they were new. "revert --pending-changes" is done on a
> branch that has just been the target of a merge, and affects changes
> that have not yet been committed.
But isn't the effect on the resulting revision DAG very similar?
> > But the issue at hand was how to hide personal comments in the commit
> > messages, not how to hide some of the intermediate changes. Why would
> > I want to do the latter?
>
> Sorry, I don't follow what do you mean with "personal comments" vs.
> "intermediate changes". I think Óscar meant that you have a branch
> with several commits, some of them meaningful, some of them of the
> "gone to lunch" variety, some reverting previous changes, etc.
Yes, I see that now, but if ttn called that ``personal junk'', then I
cannot disagree more. That's the history of my work; I don't see how
someone could object to having it in the public repository. Without
it, some changes, such as inadvertent merge mistakes, can never be
investigated and will remain a mystery forever.
I do understand that "revert --forget-merges" is one way of hiding
some of my changes from the public eye. But I don't see any
compelling use-case for that, except some marginal situations. OTOH,
my bzr experience with local branches is so short that my opinions
probably don't matter much. ;-)
Thanks.
next prev parent reply other threads:[~2010-01-08 12:52 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 17:47 log format for vc-bzr Dan Nicolaescu
2009-12-08 19:19 ` Óscar Fuentes
2009-12-08 19:47 ` Andreas Schwab
2009-12-08 20:15 ` Óscar Fuentes
2009-12-08 21:10 ` Andreas Schwab
2009-12-08 22:03 ` Dan Nicolaescu
2009-12-08 22:36 ` Óscar Fuentes
2009-12-09 0:27 ` Jason Earl
2009-12-09 8:55 ` Andreas Schwab
2009-12-09 9:55 ` Stephen J. Turnbull
2009-12-09 14:41 ` Stefan Monnier
2009-12-09 20:29 ` Óscar Fuentes
2009-12-09 21:49 ` Andreas Schwab
2009-12-09 22:34 ` Óscar Fuentes
2009-12-09 23:15 ` Andreas Schwab
2009-12-10 2:03 ` Stephen J. Turnbull
2009-12-10 9:12 ` Andreas Schwab
2009-12-10 12:28 ` Stephen J. Turnbull
2010-01-07 21:23 ` Thien-Thi Nguyen
2010-01-07 21:47 ` Óscar Fuentes
2010-01-08 0:40 ` Thien-Thi Nguyen
2010-01-08 9:00 ` Eli Zaretskii
2010-01-08 10:09 ` reversion revulsion [was: log format for vc-bzr] Thien-Thi Nguyen
2010-01-08 10:53 ` Juanma Barranquero
2010-01-08 13:41 ` reversion revulsion Thien-Thi Nguyen
2010-01-08 14:32 ` Juanma Barranquero
2010-01-08 14:47 ` Thien-Thi Nguyen
2010-01-08 11:21 ` reversion revulsion [was: log format for vc-bzr] Óscar Fuentes
2010-01-08 12:36 ` Eli Zaretskii
2010-01-08 13:27 ` reversion revulsion Óscar Fuentes
2010-01-08 16:54 ` Eli Zaretskii
2010-01-08 17:57 ` Óscar Fuentes
2010-01-08 13:29 ` reversion revulsion [was: log format for vc-bzr] Juanma Barranquero
2010-01-08 13:32 ` Juanma Barranquero
2010-01-08 10:28 ` log format for vc-bzr Juanma Barranquero
2010-01-08 12:01 ` Eli Zaretskii
2010-01-08 12:24 ` Juanma Barranquero
2010-01-08 12:52 ` Eli Zaretskii [this message]
2010-01-08 13:22 ` Juanma Barranquero
2010-01-08 13:50 ` Andreas Schwab
2010-01-08 14:28 ` Juanma Barranquero
2010-01-08 14:39 ` Thien-Thi Nguyen
2010-01-08 17:56 ` bzr Q&A [was Re: log format for vc-bzr] Glenn Morris
2010-01-09 10:35 ` Eli Zaretskii
2010-01-09 17:58 ` Stephen J. Turnbull
2010-01-08 10:50 ` log format for vc-bzr Stephen J. Turnbull
2010-01-08 12:20 ` Eli Zaretskii
2010-01-08 12:29 ` Juanma Barranquero
2010-01-08 13:39 ` Stephen J. Turnbull
2010-01-09 10:51 ` Eli Zaretskii
2010-01-08 13:48 ` Óscar Fuentes
2010-01-08 16:57 ` Eli Zaretskii
2010-01-08 17:45 ` Óscar Fuentes
2010-01-08 19:35 ` Eli Zaretskii
2010-01-08 19:41 ` Miles Bader
2010-01-08 21:22 ` Eli Zaretskii
2010-01-08 20:46 ` Óscar Fuentes
2010-01-08 21:29 ` Eli Zaretskii
2010-01-08 21:51 ` Óscar Fuentes
2010-01-08 22:24 ` Eli Zaretskii
2010-01-08 23:05 ` Óscar Fuentes
2010-01-09 8:50 ` Thien-Thi Nguyen
2010-01-09 9:36 ` Andreas Schwab
2010-01-09 13:35 ` Thien-Thi Nguyen
2010-01-09 3:45 ` Miles Bader
2010-01-08 11:54 ` Daniel Clemente
2010-01-08 16:45 ` Eli Zaretskii
2010-01-09 3:18 ` Daniel Clemente
2010-01-09 9:37 ` Eli Zaretskii
2009-12-09 1:32 ` Stefan Monnier
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=831vi0bvx5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=ofv@wanadoo.es \
/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).