git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2024, #07; Fri, 22)
Date: Mon, 25 Mar 2024 11:38:52 -0700	[thread overview]
Message-ID: <xmqqil1akvgj.fsf@gitster.g> (raw)
In-Reply-To: <ZgEcuDJfPoN-MYy5@tanuki> (Patrick Steinhardt's message of "Mon, 25 Mar 2024 07:42:00 +0100")

Patrick Steinhardt <ps@pks.im> writes:

> On Fri, Mar 22, 2024 at 05:54:26PM -0700, Junio C Hamano wrote:
>> * ps/clone-with-includeif-onbranch (2024-03-12) 1 commit
>>  - t5601: exercise clones with "includeIf.*.onbranch"
>> 
>>  An additional test to demonstrate something I am not sure what.
>> 
>>  Waiting for a review response.
>>  cf. <xmqqo7bjjid9.fsf@gitster.g>
>>  source: <0bede59a53862585c49bc635f82e44e983144a7f.1710246859.git.ps@pks.im>
>
> Based on [1] I think this topic can move forward now, right?

OK.  We may want to leave some clue to help us remember there are
still things to design (i.e., your "more thought into how this is
supposed to work"), which is far more important in the longer term
than just avoiding the BUG(), but other than that, I have no more
things to add.

Thanks.



  reply	other threads:[~2024-03-25 18:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-23  0:54 What's cooking in git.git (Mar 2024, #07; Fri, 22) Junio C Hamano
2024-03-25  6:42 ` Patrick Steinhardt
2024-03-25 18:38   ` Junio C Hamano [this message]
2024-03-25 16:39 ` Phillip Wood

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqil1akvgj.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).