You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way how getlogrange is implemented and called in other parts means commit_begin has no effect.
I propose the following fix:
Make start_date and commit_begin command line options mutually exclusive - only one of them can be defined. Error will be raised if both options are present.
Modify getxxxrange so that all combinations of start_date, commit_begin and end_only are handled correctly.
The text was updated successfully, but these errors were encountered:
fjra
added a commit
to fjra/gitstats
that referenced
this issue
May 25, 2018
I think commit 780c0fd (
start_date
command line option) introduced a bug that brokecommit_begin
command line option.The way how
getlogrange
is implemented and called in other parts meanscommit_begin
has no effect.I propose the following fix:
start_date
andcommit_begin
command line options mutually exclusive - only one of them can be defined. Error will be raised if both options are present.getxxxrange
so that all combinations ofstart_date
,commit_begin
andend_only
are handled correctly.The text was updated successfully, but these errors were encountered: