Re: How to determine the number of unique recent committers on a branch?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Mar 23 2022, Sebastian Schuberth wrote:

> On Wed, Mar 23, 2022 at 1:33 PM Ævar Arnfjörð Bjarmason
> <avarab@xxxxxxxxx> 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.




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux