From: Rogan Dawes <rogan@dawes.za.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] VoVPN-GW_100MHz: drop unsupported board configuration
Date: Wed, 27 Oct 2010 16:56:29 +0200 [thread overview]
Message-ID: <4CC83D9D.505@dawes.za.net> (raw)
In-Reply-To: <1287928835-5279-1-git-send-email-wd@denx.de>
[looks like this message got lost, resending]
On 2010/10/24 4:00 PM, Wolfgang Denk wrote:
> The 100MHz configuation of the VoVPN-GW has never been supported, so
> drop it now.
>
> Signed-off-by: Wolfgang Denk <wd@denx.de>
> ---
>
> This commit shows a problem with the concept of the "README.scrapyard"
> file: I'm supposed to enter the commit ID for the commit I'm just
> about to check in; this cannot work. Hope we remember to clean this
> up when making the next entries...
>
> Anybody having any better ideas? Some clever git attributes trick?
>
How about documenting a git command line for showing when a particular
set of lines is added?
e.g.
git blame doc/README.scrapyard
This will show the revision at which a particular line was introduced,
and will therefore provide a guide to when the feature was removed.
Include the cmdline at the top of the scrapyard file, and it should be
fairly self-evident, I would hope.
Rogan
next prev parent reply other threads:[~2010-10-27 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-24 14:00 [U-Boot] [PATCH] VoVPN-GW_100MHz: drop unsupported board configuration Wolfgang Denk
2010-10-25 18:13 ` Rogan Dawes
2010-10-26 18:40 ` Wolfgang Denk
2010-10-27 14:56 ` Rogan Dawes [this message]
2010-10-27 15:10 ` Wolfgang Denk
2010-10-27 15:17 ` Rogan Dawes
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=4CC83D9D.505@dawes.za.net \
--to=rogan@dawes.za.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.