From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: backports@vger.kernel.org
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Subject: [PATCH 0/9] backports: add kernel uploading support
Date: Wed, 22 May 2013 04:34:29 -0700 [thread overview]
Message-ID: <1369222478-30577-1-git-send-email-mcgrof@do-not-panic.com> (raw)
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
There were a few scripts left to convert to Python. One
was git-paranoia and another was gen-release.sh. This
converts both into the new framework under Python. The
new option is --kup, this would only be used by whoever
is maintaining releases for backports.
The Python gpg library didn't have support for
"--armor --detach-sign" so for now we just add
our own. For kup we add our own small wrapper.
A few thing we could do to help new maintainers or
later enhancements but we can do that later:
* Add option to import PGP keys from the trees
we manage or are reading data from.
* Add option to build tarball for non kup usage
We should just go hack up git paranoia upstream on
git itself as well.
Luis R. Rodriguez (9):
lib/bpgit.py: make git describe --long optional
lib/bpgit.py: add git describe --dirty support
lib/bpgit.py: add git status support
lib/bpgit.py: add git clean support
lib/bpgit.py: add git tree verification support
lib/bpgit.py: add support for git paranoia
lib/bpgpg.py: add simple gpg helpers for --armor --detach-sign
lib/bpkup.py: add or own kernel uploader helper lib
gentree.py: add kernel upload support
gentree.py | 211 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++--
lib/bpgit.py | 56 +++++++++++++++-
lib/bpgpg.py | 12 ++++
lib/bpkup.py | 38 +++++++++++
4 files changed, 309 insertions(+), 8 deletions(-)
create mode 100644 lib/bpgpg.py
create mode 100644 lib/bpkup.py
--
1.7.10.4
next reply other threads:[~2013-05-22 11:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 11:34 Luis R. Rodriguez [this message]
2013-05-22 11:34 ` [PATCH 1/9] lib/bpgit.py: make git describe --long optional Luis R. Rodriguez
2013-05-22 12:02 ` Johannes Berg
2013-05-22 21:49 ` Luis R. Rodriguez
2013-05-22 11:34 ` [PATCH 2/9] lib/bpgit.py: add git describe --dirty support Luis R. Rodriguez
2013-05-22 11:34 ` [PATCH 3/9] lib/bpgit.py: add git status support Luis R. Rodriguez
2013-05-22 12:02 ` Johannes Berg
2013-05-23 0:28 ` Luis R. Rodriguez
2013-05-22 11:34 ` [PATCH 4/9] lib/bpgit.py: add git clean support Luis R. Rodriguez
2013-05-22 12:03 ` Johannes Berg
2013-05-23 0:28 ` Luis R. Rodriguez
2013-05-22 11:34 ` [PATCH 5/9] lib/bpgit.py: add git tree verification support Luis R. Rodriguez
2013-05-22 11:34 ` [PATCH 6/9] lib/bpgit.py: add support for git paranoia Luis R. Rodriguez
2013-05-22 12:05 ` Johannes Berg
2013-05-23 0:37 ` Luis R. Rodriguez
2013-05-23 15:25 ` Johannes Berg
2013-05-23 21:02 ` Luis R. Rodriguez
2013-05-28 20:02 ` Luis R. Rodriguez
2013-05-28 20:14 ` Luis R. Rodriguez
2013-05-28 20:23 ` Johannes Berg
2013-07-27 17:11 ` Luis R. Rodriguez
2013-05-28 20:17 ` Johannes Berg
2013-05-22 11:34 ` [PATCH 7/9] lib/bpgpg.py: add simple gpg helpers for --armor --detach-sign Luis R. Rodriguez
2013-05-22 11:34 ` [PATCH 8/9] lib/bpkup.py: add or own kernel uploader helper lib Luis R. Rodriguez
2013-05-22 12:06 ` Johannes Berg
2013-05-23 0:43 ` Luis R. Rodriguez
2013-05-22 11:34 ` [PATCH 9/9] gentree.py: add kernel upload support Luis R. Rodriguez
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=1369222478-30577-1-git-send-email-mcgrof@do-not-panic.com \
--to=mcgrof@do-not-panic.com \
--cc=backports@vger.kernel.org \
/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.