git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Sebastian Schuberth <sschuberth@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: How to determine the number of unique recent committers on a branch?
Date: Wed, 23 Mar 2022 15:47:42 +0100	[thread overview]
Message-ID: <220323.86bkxwogxs.gmgdl@evledraar.gmail.com> (raw)
In-Reply-To: <CAHGBnuMRKhsF-xCL944KD5GFPWYe-9cSp6FBZfaZ7bdVTkgjng@mail.gmail.com>


On Wed, Mar 23 2022, Sebastian Schuberth wrote:

> On Wed, Mar 23, 2022 at 1:33 PM Ævar Arnfjörð Bjarmason
> <avarab@gmail.com> wrote:
>
>> I think --since to "rev-list" combined with e.g. "shortlog" is what you
>> want here, e.g. on git.git:
>>
>>         $ git -P shortlog --since=2.weeks.ago -sn origin/master
>
> But that still interprets "2.weeks.ago" relative to today, right? So,
> for a repo to which no one committed to in the last 2 weeks, it would
> show nothing. But what I'd like to get is the number of committers
> since 2 weeks before the latest commit. Any idea how to get that
> easily?

Ah, sorry. I managed to (mis)read your question.

Perhaps there's a way to do that in one command, but I don't think so,
but I may be wrong.

But you *can* do by grabbing the epoch from the tip commit and doing
some basic shell-math on it:

    git log --since=$(($(git log --oneline -1 --date=unix --pretty=format:%ad origin/master) - $((60*60*24*7*2)) )) origin/master

It would be nice if we had some option to to do that, e.g.:

    git log --since=2.weeks.ago --date-now=February.2018

Or To get you things in late January 2018. Or even:

    git -c core.time="February.2018" log --since=2.weeks.ago

To fool the entirety of git to use a given time() as current (but of
course it would also need to "adjust back" commit dates for relative
--since).

I'm 99% sure we don't have that, especially from looking at some of the
code just now. But in the meantime you can hack it as above.

  reply	other threads:[~2022-03-23 14:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 10:23 How to determine the number of unique recent committers on a branch? Sebastian Schuberth
2022-03-23 12:30 ` Ævar Arnfjörð Bjarmason
2022-03-23 13:00   ` Sebastian Schuberth
2022-03-23 14:47     ` Ævar Arnfjörð Bjarmason [this message]
2022-03-23 22:14       ` Sebastian Schuberth
2022-03-23 20:48 ` Junio C Hamano

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=220323.86bkxwogxs.gmgdl@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=sschuberth@gmail.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).