From: Junio C Hamano <gitster@pobox.com>
To: Miklos Vajna <vmiklos@vmiklos.hu>
Cc: git@vger.kernel.org
Subject: Re: git log --since to not stop after first old commit?
Date: Thu, 07 Apr 2022 19:30:33 -0700 [thread overview]
Message-ID: <xmqqv8vkpara.fsf@gitster.g> (raw)
In-Reply-To: Yk8Gvf/fjVca9hDB@vmiklos.hu
Miklos Vajna <vmiklos@vmiklos.hu> writes:
> On Fri, Apr 01, 2022 at 10:51:34AM -0700, Junio C Hamano <gitster@pobox.com> wrote:
>> We could add a --since-as-filter= option or something, but then the
>> user needs to be careful when to stop (and digging down to the root
>> of the history, i.e. "never stop", may be an acceptable answer to
>> some projects).
>
> I sent a patch to add such an option (which picks the "never stop"
> behavior) on 1st, did you see that?
>
> If the idea is OK in principle, but the patch needs tweaking, please let
> me know.
As a single-shot change, "--since-as-filter" is certainly an easy to
explain approach of least resistance.
But when viewed from a higher level as a general design problem, I
am unsure if it is a good direction to go in.
Giving "--since" the "as-filter" variant sets a precedent, and
closes the door for a better UI that we can extend more generally
without having to add "--X-as-filter" for each and every conceivable
"--X" that is a traversal stopper into a filtering kind.
next prev parent reply other threads:[~2022-04-08 2:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 8:21 git log --since to not stop after first old commit? Miklos Vajna
2022-04-01 9:57 ` Ævar Arnfjörð Bjarmason
2022-04-01 10:14 ` Miklos Vajna
2022-04-01 13:51 ` Ævar Arnfjörð Bjarmason
2022-04-01 17:51 ` Junio C Hamano
2022-04-01 21:36 ` [PATCH] git-log: add a --since-as-filter option Miklos Vajna
2022-04-02 10:09 ` [PATCH v2] " Miklos Vajna
2022-04-07 15:43 ` git log --since to not stop after first old commit? Miklos Vajna
2022-04-08 2:30 ` Junio C Hamano [this message]
2022-04-08 18:19 ` Junio C Hamano
[not found] ` <CANgJU+Wr+tKNPfeh4dst-E_LSnoYYmN1easqmkFUA9spp-rpKQ@mail.gmail.com>
2022-04-11 6:37 ` Miklos Vajna
2022-04-11 9:18 ` demerphq
2022-04-11 16:58 ` Junio C Hamano
2022-04-22 18:48 ` Junio C Hamano
2022-04-22 20:01 ` [PATCH v6] log: "--since-as-filter" option is a non-terminating "--since" variant Miklos Vajna
2022-04-22 22:11 ` Junio C Hamano
2022-04-22 23:43 ` Junio C Hamano
2022-04-23 12:59 ` [PATCH v7] " Miklos Vajna
2022-04-08 21:01 ` [PATCH v3] git-log: add a --since=... --as-filter option Miklos Vajna
2022-04-12 8:47 ` Ævar Arnfjörð Bjarmason
2022-04-15 20:39 ` [PATCH v4] " Miklos Vajna
2022-04-15 23:13 ` Junio C Hamano
2022-04-16 14:23 ` [PATCH v5] log: "--as-filter" option adjusts how "--since" cut-off works Miklos Vajna
2022-04-22 6:50 ` Miklos Vajna
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=xmqqv8vkpara.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=vmiklos@vmiklos.hu \
/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).