git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: viresh kumar <viresh.kumar@linaro.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [Query] Can we ignore case for commiters name in shortlog?
Date: Fri, 30 Nov 2012 07:39:03 +0530	[thread overview]
Message-ID: <CAOh2x==NBeeoE2=PhaDC143ZF_xHKD5m=Po+-DS2X43CEeGiEQ@mail.gmail.com> (raw)

Hi Junio and others,

I have a query. git shortlog lists the patches submitted per commiter, like:

> Viresh Kumar (7):
>       cpufreq: Improve debug prints
>       cpufreq: return early from __cpufreq_driver_getavg()
>       cpufreq: governors: remove redundant code
>       cpufreq: Fix sparse warnings by updating cputime64_t to u64
>       cpufreq: Fix sparse warning by making local function static
>       cpufreq: Avoid calling cpufreq driver's target() routine if target_freq == policy->cur
>       cpufreq: Make sure target freq is within limits

> viresh kumar (3):
>       cpufreq / core: Fix typo in comment describing show_bios_limit()
>       cpufreq / core: Fix printing of governor and driver name
>       cpufreq: Move common part from governors to separate file, v2

I know, there was something wrong at my end and i have commited stuff
with different cases.

I was just thinking if we can ignore case for commiter name while
listing stuff here?
So, that we get over any manual mistakes from commiter.

--
viresh

             reply	other threads:[~2012-11-30  2:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-30  2:09 viresh kumar [this message]
2012-11-30  3:24 ` [Query] Can we ignore case for commiters name in shortlog? David Aguilar
2012-11-30  3:32   ` Viresh Kumar
2012-11-30 13:01   ` Damien Robert
2012-11-30  3:33 ` Nicolas Pitre
2012-11-30  3:35   ` Viresh Kumar
2012-11-30 11:19     ` Max Horn
2012-11-30 15:05       ` Viresh Kumar
2012-11-30 13:07 ` Andreas Schwab

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='CAOh2x==NBeeoE2=PhaDC143ZF_xHKD5m=Po+-DS2X43CEeGiEQ@mail.gmail.com' \
    --to=viresh.kumar@linaro.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).