public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Michael Schwingen <rincewind@discworld.dascon.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] IXP42x patch series version 3
Date: Sun, 13 Feb 2011 18:03:18 +0100	[thread overview]
Message-ID: <4D580ED6.8050404@discworld.dascon.de> (raw)
In-Reply-To: <AANLkTi=X9OB2CD6WtxyeNn4=AAKm1KGf9mEs7eDM9Ftu@mail.gmail.com>

Am 02/07/2011 09:54 PM, schrieb Graeme Russ:
> On Tue, Feb 8, 2011 at 7:37 AM, Michael Schwingen
> <rincewind@discworld.dascon.de> wrote:
>> Am 02/05/2011 12:52 AM, schrieb Wolfgang Denk:
>>> Dear Michael Schwingen,
>>>
>>> In message <1296860763-16149-1-git-send-email-michael@schwingen.org> you wrote:
>>>> here is the third incarnation of the IXP patch series. I hope I addressed
>>>> all the comments from version 2:
>>>>  - timer system now uses no BSS-based variables
>>>>  - use I/O accessors
>>>>  - remove config.mk from board directories
>>>>  - set -ffunction-sections/--gc-sections globally (for IXP architecture)
>>> Sorry, but please consider it all NAKed.
>>>
>>> See the note at bullet 2 at
>>> http://www.denx.de/wiki/view/U-Boot/Patches#Sending_updated_patch_versions
>>> for the rationale.
>> Hi,
>>
>> I just tried, but I can't find a way to insert the changelog so that
>> git-send-email places it at the required point (ie. after the s.o.b. and
>> inside the same comment block as the diffstat) - all I could get was the
>> changelog inside the comment block, with a line with "---" above, like this:
>>
>> From: Michael Schwingen <michael@schwingen.org>
>> Date: Fri, 4 Feb 2011 21:34:59 +0100
>> Subject: [PATCH 01/17] add XScale sub architecture (IXP/PXA) to
>> maintainer list
>>
>> ---
>> Changes for V2:
>> Changes for V3:
>>  - change patch description
>>  - drop wepep250 (should already be deleted)
>> Changes for V4:
>>  - add changelog
>>
>> Signed-off-by: Michael Schwingen <michael@schwingen.org>
>> ---
>>  MAINTAINERS |   44 ++++++++++++++++++++++----------------------
>>  1 files changed, 22 insertions(+), 22 deletions(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index b37ed0c..709c5d9 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -559,8 +559,8 @@ Stefano Babic <sbabic@denx.de>
>>
>> which looks quite different from what the wiki suggests.
>>
>> Do you have a short pointer how to get the right result using git? Or is
>> this format actually acceptable?
>>
> I use git-format-patch to dump the patches into a directory and then tweak
> the comment section manually before using git-send-email. I can also run
> diff against any two versions of the series, checkpatch etc
>
> Maybe there is a more integrated way, but I'm a creature of habit - once I
> find something that works for me, I tend to stick to it :)
manually editing the changelog in 17 files for every patch version does
not sound very manageable. Is there really no way to generate/maintain
the changelogs using git?

cu
Michael

  reply	other threads:[~2011-02-13 17:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-04 23:05 [U-Boot] IXP42x patch series version 3 Michael Schwingen
2011-02-04 23:05 ` [U-Boot] [PATCH 01/17] add XScale sub architecture (IXP/PXA) to maintainer list Michael Schwingen
2011-02-04 23:05 ` [U-Boot] [PATCH 02/17] add support for IXP42x Rev. B1 and newer Michael Schwingen
2011-02-04 23:05 ` [U-Boot] [PATCH 03/17] trigger hardware watchdog in IXP42x serial driver Michael Schwingen
2011-02-04 23:05 ` [U-Boot] [PATCH 04/17] Fix IXP code to work after relocation was added Michael Schwingen
2011-02-04 23:05 ` [U-Boot] [PATCH 05/17] fix "depend" target in npe directory Michael Schwingen
2011-02-04 23:05 ` [U-Boot] [PATCH 06/17] support CONFIG_SYS_LDSCRIPT on ARM Michael Schwingen
2011-02-04 23:05 ` [U-Boot] [PATCH 07/17] use -ffunction-sections / --gc-sections on IXP42x Michael Schwingen
2011-02-04 23:05 ` [U-Boot] [PATCH 08/17] update/fix AcTux1 board Michael Schwingen
2011-02-04 23:05 ` [U-Boot] [PATCH 09/17] update/fix AcTux2 board Michael Schwingen
2011-02-04 23:05 ` [U-Boot] [PATCH 10/17] update/fix AcTux3 board Michael Schwingen
2011-02-04 23:05 ` [U-Boot] [PATCH 11/17] update/fix AcTux4 board Michael Schwingen
2011-02-04 23:05 ` [U-Boot] [PATCH 12/17] IXP NPE: add support for fixed-speed MII ports Michael Schwingen
2011-02-04 23:05 ` [U-Boot] [PATCH 13/17] add dvlhost (dLAN 200 AV Wireless G) board Michael Schwingen
2011-02-04 23:06 ` [U-Boot] [PATCH 14/17] update/fix IXDP425 / IXDPG425 boards Michael Schwingen
2011-02-04 23:06 ` [U-Boot] [PATCH 15/17] update/fix PDNB3 board Michael Schwingen
2011-02-07  9:58   ` Stefan Roese
2011-02-04 23:06 ` [U-Boot] [PATCH 16/17] IXP42x PCI rewrite Michael Schwingen
2011-02-04 23:06 ` [U-Boot] [PATCH 17/17] run arm_pci_init after relocation Michael Schwingen
2011-02-04 23:52 ` [U-Boot] IXP42x patch series version 3 Wolfgang Denk
2011-02-07 20:37   ` Michael Schwingen
2011-02-07 20:54     ` Graeme Russ
2011-02-13 17:03       ` Michael Schwingen [this message]
2011-02-13 21:13         ` Graeme Russ
2011-02-13 22:03           ` Wolfgang Denk
2011-02-13 22:18             ` Graeme Russ
2011-02-13 23:38             ` Michael Schwingen
2011-02-14 12:00               ` Albert ARIBAUD
2011-02-15 18:50                 ` Michael Schwingen
2011-02-16 21:59                 ` [U-Boot] IXP42x patch series version 3 - patch summaries Michael Schwingen

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=4D580ED6.8050404@discworld.dascon.de \
    --to=rincewind@discworld.dascon.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