From: Andy Pont <andy.pont@sdcsystems.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] RFC - PatchTrack Specification (revised)
Date: Wed, 25 Jul 2012 11:36:24 +0100 [thread overview]
Message-ID: <004e01cd6a51$57d5ff70$0781fe50$@pont@sdcsystems.com> (raw)
In-Reply-To: <20120724184108.47517200247@gemini.denx.de>
Wolfgang wrote...
> > A revised version of the spec (sorry, I would have used reply-to but
> > something went amiss with gmail and I've lost the original)
>
> http://www.denx.de/wiki/U-Boot/ToolsPatchTracking updated.
I have been and had a look at the specification that you have posted and am
happy to get my hands dirty helping with implement and test this.
I know that a good proportion (possibly even all of it) could be implemented
in Python but is there a preference or consensus on what would be the best
language to do it in?
Regards,
Andy.
next prev parent reply other threads:[~2012-07-25 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 13:48 [U-Boot] RFC - PatchTrack Specification (revised) Graeme Russ
2012-07-24 18:41 ` Wolfgang Denk
2012-07-24 22:33 ` Graeme Russ
2012-07-25 10:36 ` Andy Pont [this message]
2012-07-25 11:00 ` Wolfgang Denk
2012-07-25 12:50 ` Graeme Russ
2012-07-29 3:15 ` Marek Vasut
2012-07-29 3:49 ` Graeme Russ
2012-09-22 14:44 ` Marek Vasut
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='004e01cd6a51$57d5ff70$0781fe50$@pont@sdcsystems.com' \
--to=andy.pont@sdcsystems.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