From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: ChangeLog: move arch-specific entries into the arch dir
Date: Thu, 07 Jan 2021 13:57:14 -0700 [thread overview]
Message-ID: <87tursv51x.fsf@tromey.com> (raw)
In-Reply-To: <20210107171236.GJ7494@vapier> (Mike Frysinger via Gdb-patches's message of "Thu, 7 Jan 2021 12:12:36 -0500")
Mike> merging them into one causes extra pain due to conflicts. having sep
Mike> arch ones alleviates that a little as you don't normally have people
Mike> working on the same arch at the same time.
Mike> ideally we'd throw away these archaic ChangeLog files entirely. they
Mike> are a huge waste of time for everyone and would be much better served
Mike> writing proper git commit messages. it isn't the 80s/90s anymore.
I'm +1 on that, but other maintainers like them, so we've been keeping
them around.
For conflicts, I do this:
https://gnu.wildebeest.org/blog/mjw/2012/03/16/automagically-merging-changelog-files-with-mercurial-or-git/
I rarely have ChangeLog conflicts or snafus. I can't really recall the
last one.
Tom
next prev parent reply other threads:[~2021-01-07 20:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 8:09 Mike Frysinger via Gdb-patches
2021-01-07 9:33 ` Andrew Burgess
2021-01-07 17:12 ` Mike Frysinger via Gdb-patches
2021-01-07 20:57 ` Tom Tromey [this message]
2021-01-08 2:03 ` Mike Frysinger via Gdb-patches
2021-01-09 20:15 ` Tom Tromey
2021-01-08 9:57 ` Andrew Burgess
2021-01-09 17:02 ` Simon Marchi via Gdb-patches
2021-01-09 19:35 ` Mike Frysinger via Gdb-patches
2021-01-09 20:12 ` Tom Tromey
2021-01-10 3:26 ` Mike Frysinger via Gdb-patches
2021-01-11 11:10 ` Andrew Burgess
2021-01-11 12:22 ` Mike Frysinger via Gdb-patches
2021-01-07 12:14 ` Jose E. Marchesi via Gdb-patches
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=87tursv51x.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox