All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>
Subject: Re: [PATCH 6/9] lib/bpgit.py: add support for git paranoia
Date: Tue, 28 May 2013 22:23:35 +0200	[thread overview]
Message-ID: <1369772615.8548.30.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6Up+L2b_nQoLND4NrSD+J3ydKsnpP=178WhPFMSV4D6kQ@mail.gmail.com> (sfid-20130528_221443_210848_7453C4C7)

On Tue, 2013-05-28 at 13:14 -0700, Luis R. Rodriguez wrote:

> Addressing RELMOD_TYPE seems easy with --git-revision, add arguments
> additional arguments: -s -n -p -c -u as release mode specifications as
> arguments to be passed to gentree.py either as:
> 
>   a) standalone arguments, or;
>   b) as a conglomeration of release modification types, ie something
> like --rel-mod=snpcu

I think this would fit better with the model of a separate tool, that
calls the gentree code to generate internally. Then you'd have maybe 

./devel/gen-and-kup.py -s -n -p -c -u ...

or something? Overall, that seems cleaner than cluttering gentree.py
with all these options, although gentree.py would probably (internally
only?) have to learn about being able to take patches and the skeleton
code from another directory to address the paranoia for the backport
tree itself.

> We just need a reasonable way to address RELMOD_UPDATE then. 

That's when you generate a new one for the same tag, due to updates,
right?

I don't really know how to handle this -- we don't really have a
canonical database of what we've generated before.

johannes


  reply	other threads:[~2013-05-28 20:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 11:34 [PATCH 0/9] backports: add kernel uploading support Luis R. Rodriguez
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 [this message]
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=1369772615.8548.30.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=backports@vger.kernel.org \
    --cc=mcgrof@do-not-panic.com \
    /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.