From: Jason Earl <jearl@notengoamigos.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>,
"Andreas Schwab" <schwab@linux-m68k.org>,
emacs-devel@gnu.org
Subject: Re: log format for vc-bzr
Date: Tue, 08 Dec 2009 17:27:45 -0700 [thread overview]
Message-ID: <87hbs1at4u.fsf@notengoamigos.org> (raw)
In-Reply-To: <200912082203.nB8M3FLP023771@godzilla.ics.uci.edu> (Dan Nicolaescu's message of "Tue, 8 Dec 2009 14:03:15 -0800 (PST)")
Dan Nicolaescu <dann@ics.uci.edu> writes:
> Andreas Schwab <schwab@linux-m68k.org> writes:
>
> > Óscar Fuentes <ofv@wanadoo.es> writes:
> >
> > > Useless for whom? For the developer who is working on the
> > > feature? No, they are small milestones and state-savers (for
> > > synchronizing his desktop with his laptop, for instance). For
> > > the other developers? Yes, but that's the reason why merged
> > > history is hidden by default.
> >
> > Such a useless commit history should never be published in the
> > first place.
>
> And to build on your argument: if the developer decides to put
> something in a log, then it must be relevant, so we should show it by
> default.
Really? Perhaps I am just showing my ignorance, but I make trivial
commits all of the time with bzr. As Óscar pointed out I will often
commit with a message like "Switching to main desktop" or "Time to go
home." This might seem like junk (and it mostly is junk), but I have
surprised myself quite a few times by actually using these cues to
remember why it was that I left off where I did.
That doesn't mean that I want all of these commit messages to show up in
the log when I do bzr log on the mainline. As a bzr user I personally
think that bzr has the right default in this case. While working on a
feature or fixing a bug I can use the commit message to remind me what I
am doing. When I finally merge, however, I need to create a commit
message that is more substantial.
I suppose that git users use rebase to erase all of the "junk" commit
messages. From what I understand I can do the same with bzr. However,
if I want to work on the same patch on more than one machine doing
things this way seems to raise the level of difficulty high enough that
I can't figure out how to do it :).
Now, obviously, you can write vc-mode so that it shows commit messages
that bzr log hides by default, but this will be quite surprising to
people that use bzr.
Jason
next prev parent reply other threads:[~2009-12-09 0:27 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hbs1at4u.fsf@notengoamigos.org \
--to=jearl@notengoamigos.org \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
--cc=schwab@linux-m68k.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.