public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Proposed CHANGELOG Generation Helpers
Date: Fri, 13 Oct 2006 09:28:40 -0500	[thread overview]
Message-ID: <E1GYO1g-00053q-21@jdl.com> (raw)
In-Reply-To: Your message of "Fri, 13 Oct 2006 11:52:21 +0200." <20061013095221.AC2B1353C95@atlas.denx.de>

So, like, the other day Wolfgang Denk mumbled:
> Dear Jon,
> 
> Thanks a lot for the suggestions.

Most welcome.

> > If either of these is close, it might be a pretty simple mod
> > to, say, the "git shortlog" script to make it more acceptable.
> 
> A variation of (2) is perfectly fine with me:

Excellent.

> So since I seem to be the only person on this  planet  who  likes  to
> have this CHANGELOG file, and it has caused so much trouble already I
> suggest the following procedure:
>
> ...
> 
> Is this acceptable to you and everybody else?

This is really good!  Thanks!

Having the baseline 85xx and FDT parts from Matthew will
make much of this vastly easier for the 86xx changes!

Thank you.

jdl

  parent reply	other threads:[~2006-10-13 14:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13  1:14 [U-Boot-Users] Proposed CHANGELOG Generation Helpers Jon Loeliger
2006-10-13  9:52 ` Wolfgang Denk
2006-10-13 13:24   ` [U-Boot-Users] CHANGELOG w/ status update: cmd_of.c, ft_build.c, vsprintf.c, long long print problem Jerry Van Baren
2006-10-13 13:37     ` Wolfgang Denk
2006-10-13 13:45       ` Jerry Van Baren
2006-10-13 14:37     ` Jon Loeliger
2006-10-13 14:52       ` Jerry Van Baren
2006-10-13 14:28   ` Jon Loeliger [this message]
2006-10-13 14:32   ` [U-Boot-Users] Proposed CHANGELOG Generation Helpers Jon Loeliger
2006-10-13 15:33   ` Timur Tabi
2006-10-16  7:14     ` Wolfgang Denk
2006-10-16 14:36   ` Grant Likely

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=E1GYO1g-00053q-21@jdl.com \
    --to=jdl@jdl.com \
    --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