Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: stanshebs@earthlink.net, stan@codesourcery.com,
	gdb-patches@sources.redhat.com
Subject: Re: Subdir ChangeLogs
Date: Fri, 01 Aug 2008 19:25:00 -0000	[thread overview]
Message-ID: <ubq0cmtcg.fsf@gnu.org> (raw)
In-Reply-To: <m37ib0zhu5.fsf@fleche.redhat.com>

> Cc: Stan Shebs <stanshebs@earthlink.net>, stan@codesourcery.com,         gdb-patches@sources.redhat.com
> From: Tom Tromey <tromey@redhat.com>
> Date: Fri, 01 Aug 2008 12:54:42 -0600
> 
> Eli> You asked for opinions, so here's mine: I don't really understand why
> Eli> we'd want to do this.  The only reason I heard so far was that it will
> Eli> help when source and doc files are committed together.
> 
> It means less busy-work.  Right now when I prepare a patch I usually
> edit at least two ChangeLogs, sometimes three or four.

Well, I use Emacs, which brings me to the right ChangeLog
automagically.  Once I'm in the right file, the rest doesn't matter,
since I need to write the text for each entry anyway.

> Then I have to redo that when re-applying the patch for checkin.
> And, then there is more editing preparing the commit message.

Looks like your tools are not set up in an optimal way.  For example,
the commit messages are usually just copies of the log entries, so
it's just copy-paste.  How hard can that be?

But as I said: I'm not going to fight against this.


  reply	other threads:[~2008-08-01 19:25 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-13  0:16 RFA: Remove gdb-events Tom Tromey
2008-07-13  3:26 ` Stan Shebs
2008-07-13 21:56   ` Tom Tromey
2008-08-01 16:20     ` Tom Tromey
2008-08-01 16:33       ` Subdir ChangeLogs (was Re: RFA: Remove gdb-events) Stan Shebs
2008-08-01 17:10         ` Subdir ChangeLogs Tom Tromey
2008-08-01 17:27           ` Stan Shebs
2008-08-01 17:54             ` Tom Tromey
2008-08-01 18:44             ` Eli Zaretskii
2008-08-01 18:55               ` Tom Tromey
2008-08-01 19:25                 ` Eli Zaretskii [this message]
2008-08-01 19:33                   ` Tom Tromey
2008-08-01 20:11                     ` Thiago Jung Bauermann
2008-08-02  7:13                     ` Eli Zaretskii
2008-08-02 16:52                       ` Tom Tromey
2008-08-02 17:28                         ` Eli Zaretskii
2008-08-02 20:24                         ` Thiago Jung Bauermann
2008-08-03  0:02           ` Michael Snyder
2008-08-01 17:40       ` RFA: Remove gdb-events Mark Kettenis
2008-07-14 17:10 ` Joel Brobecker
2008-07-14 20:33   ` Tom Tromey
2008-07-15  6:54     ` Joel Brobecker
2008-07-17 23:41   ` Tom Tromey
2008-07-21 16:54     ` GDB/MI PING (was: "Re: RFA: Remove gdb-events") Joel Brobecker
2008-07-22  0:56     ` RFA: Remove gdb-events Tom Tromey
2008-07-25 16:11       ` Tom Tromey
2008-07-20 11:46 ` Eli Zaretskii
2008-07-21 17:13 ` Vladimir Prus
2008-07-22  0:32   ` Tom Tromey

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=ubq0cmtcg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=stan@codesourcery.com \
    --cc=stanshebs@earthlink.net \
    --cc=tromey@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox