From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] remove main CHANGELOG file
Date: Wed, 05 May 2010 22:58:02 +0200 [thread overview]
Message-ID: <20100505205802.97211B0FF81@gemini.denx.de> (raw)
In-Reply-To: <1273091842.2451.4563.camel@localhost.localdomain>
Dear Peter Tyser,
In message <1273091842.2451.4563.camel@localhost.localdomain> you wrote:
>
> I still don't grasp what the common use of looking at U-Boot's entire
> changelog is. What are some common tasks that require grepping U-Boot's
> entire changelog? Are these tasks performed frequently enough that the
> extra <1 second 'git log' requires is bothersome?
I'm trying to maintain some awareness of open patches. For example,
when I receive a pull request I mark all included patches as
processed; sometimes this includes tracking down older versions of
the patches, or commit messages that have been changed on the way.
And yes, the <1 second delay is bothersome when doing this frequently
enough.
> > -> wget -O u-boot.tgz 'http://git.denx.de/?p=u-boot.git;a=snapshot;sf=tgz'
>
> For snapshots, the CHANGELOG file is going to be out of date though.
> It'll only list the changes that occurred up to the previous release.
> This seems worse than not having a CHANGELOG at all as its actively
> misleading people as to what changes their source code has.
I disagree here. I find myself quite frequently in the situation that
I have to identify the exact version some source tree has been
derived from. Companies who maintain out-of-tree ports usually don't
include any SCM information either. To me, the CHANGELOG is an
extremely useful resource in such cases.
> I'll quit whining, just wanted to give my +1 for removing the changelog.
I don't consider you whining. I am listening to the arguments.
I am not convinced yet, though.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The human race is faced with a cruel choice: work or daytime tele-
vision.
next prev parent reply other threads:[~2010-05-05 20:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 2:16 [U-Boot] [PATCH 2/2] remove main CHANGELOG file Kim Phillips
2010-05-04 21:41 ` Wolfgang Denk
2010-05-05 0:25 ` Kim Phillips
2010-05-05 6:54 ` Wolfgang Denk
2010-05-05 13:51 ` Marek Vasut
2010-05-05 14:17 ` Wolfgang Denk
2010-05-05 14:56 ` Timur Tabi
2010-05-05 15:07 ` Wolfgang Denk
2010-05-05 16:03 ` Peter Tyser
2010-05-05 19:05 ` Wolfgang Denk
2010-05-05 19:45 ` Scott Wood
2010-05-05 20:36 ` Wolfgang Denk
2010-05-05 20:37 ` Peter Tyser
2010-05-05 20:58 ` Wolfgang Denk [this message]
2010-05-05 21:43 ` Peter Tyser
2010-05-05 21:51 ` Wolfgang Denk
2010-07-16 18:44 ` Kim Phillips
2010-05-05 21:06 ` Kim Phillips
2010-05-05 21:07 ` Wolfgang Denk
2010-05-05 21:09 ` Kim Phillips
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=20100505205802.97211B0FF81@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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