All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Florian Mickler <florian@mickler.org>
Cc: linux-kernel@vger.kernel.org,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Wolfram Sang <w.sang@pengutronix.de>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Stephen Hemminger <shemminger@vyatta.com>,
	Stefan Richter <stefanr@s5r6.in-berlin.de>,
	Greg KH <greg@kroah.com>
Subject: Re: [RFC PATCH] scripts/get_maintainer.pl: add interactive mode
Date: Mon, 20 Sep 2010 17:38:52 -0700	[thread overview]
Message-ID: <1285029532.25988.82.camel@Joe-Laptop> (raw)
In-Reply-To: <20100920235337.6e0ac989@schatten.dmk.lab>

On Mon, 2010-09-20 at 23:53 +0200, Florian Mickler wrote:
> On Mon, 20 Sep 2010 12:43:08 -0700
> Joe Perches <joe@perches.com> wrote:
> > #(toggle), A#(author), S#(signed) *(all), ^(none), O(options), Y(approve): 
> I don't think the descriptions on the bottom are that descriptive. Nor
> can they be. There should probably be just a quick primer like:
> "([N]+:select) ([N]-:deselect) ([N]?:toggle infos) (Y:approve) (h:help)"
> and on "h" a long description gets displayed.

We disagree.  There could be a useful "H" help option.

> > Because git history is now not searched by default
> > when there is a named maintainer, there are no
> > commit signers.
> 
> Don't know if this is intuitive. If there is the possibility to have
> them shown but not selected, that would be ideal as it relieves the
> user from pressing extra keys while still having a sane behaviour.

Use a command line option: --git.

All command line options apply to create the initial list of
displayed names.

Or add code to set

	$git-fallback = 1 if $interactive;

> > 
> > If the "G" option is entered, you get:
> > 
> > #(toggle), A#(author), S#(signed) *(all), ^(none), O(options), Y(approve): g
> > --------------------------------------------------------------------------------
> > *  # email/list and role:stats                                        auth sign
> > *  1 Stephen Hemminger <shemminger@linux-foundation.org>                 1    0
> >      maintainer:SKGE, SKY2 10/100...,commit_signer:38/69=55%
> >    2 "David S. Miller" <davem@davemloft.net>                             7   57
> >      commit_signer:57/69=83%
> >    3 Mike McCormack <mikem@ring3k.org>                                  16   16
> >      commit_signer:16/69=23%
> >    4 Joe Perches <joe@perches.com>                                       4    4
> >      commit_signer:4/69=6%
> > *  5 netdev@vger.kernel.org                                           
> >      open list:SKGE, SKY2 10/100...
> > *  6 linux-kernel@vger.kernel.org                                     
> >      open list
> 
> I would try to fit reviewed-by in the statistics on the right, because
> that actually says a bit about the ability and willingness to review
> code... 

I think it's not worth it.

Only about 2% of signatures in git history are reviewed-by:

Using S shows the signature type.

Over the last year:
$ git log --since=1-year-ago | grep -i "by:.*@" | \
  cut -f1 -d":" | sort -i | uniq -ci | sort -rn | head -10
  83413     Signed-off-by
   6544     Acked-by
   2022     Reviewed-by
   1691     Reported-by
   1065     Tested-by
    111     Reported-and-tested-by
     83     Suggested-by
     31     Requested-by
     28         Signed-off-by
     26     Fixed-by

> [snip menu parsing code]
> 
> That should probably go in an extra function and be slimmed down, like
> I did in a later version I sent you.

Maybe.  I think it doesn't matter much though.
Menu handling code tends to get long.

> > +sub bool_invert {
> > +    my ($bool_ref) = @_;
> > +
> > +    if ($$bool_ref) {
> > +	$$bool_ref = 0;
> > +    } else {
> > +	$$bool_ref = 1;
> > +    }
>  +}
> 
> That should just be $$bool_ref = !$$bool_ref (and probably not a
> function)

I think it needs to be a function.
I want a 0 or 1, not "" or 1.



  parent reply	other threads:[~2010-09-21  0:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 12:13 [PATCH rfc] scripts/get_maintainer.pl: add interactive mode florian
2010-09-15 13:43 ` [v2 PATCH " florian
2010-09-15 15:16   ` [PATCH RFC v3] " florian
2010-09-15 15:35     ` Joe Perches
2010-09-20 19:43     ` [RFC PATCH] " Joe Perches
2010-09-20 21:53       ` Florian Mickler
2010-09-20 22:27         ` [PATCH] scripts/get_maintainer.pl: fix .mailmap handling florian
2010-09-20 22:35           ` florian
2010-09-21  0:14             ` Joe Perches
2010-09-21  4:59               ` Florian Mickler
2010-09-21  5:20                 ` Joe Perches
2010-09-21  6:23                   ` Florian Mickler
2010-09-21  0:38         ` Joe Perches [this message]
2010-09-21  5:31           ` [RFC PATCH] scripts/get_maintainer.pl: add interactive mode Florian Mickler
2010-09-21  6:12             ` Joe Perches
2010-09-21  6:30               ` [PATCH v2] scripts/get_maintainer.pl: fix mailmap handling florian
2010-09-15 15:27   ` [v2 PATCH rfc] scripts/get_maintainer.pl: add interactive mode Joe Perches
2010-09-16  8:30     ` Florian Mickler

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=1285029532.25988.82.camel@Joe-Laptop \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=ebiederm@xmission.com \
    --cc=florian@mickler.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=stefanr@s5r6.in-berlin.de \
    --cc=w.sang@pengutronix.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.