From: Junio C Hamano <email@example.com> To: Ævar Arnfjörð Bjarmason <firstname.lastname@example.org> Cc: email@example.com Subject: Re: What's cooking in git.git (Jan 2018, #02; Tue, 9) Date: Wed, 10 Jan 2018 12:02:50 -0800 Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Ævar Arnfjörð Bjarmason <firstname.lastname@example.org> writes: > On Tue, Jan 09 2018, Junio C. Hamano jotted: > >> * ab/wildmatch-tests (2018-01-04) 7 commits >> (merged to 'next' on 2018-01-09 at 09f0b84098) >> + wildmatch test: create & test files on disk in addition to in-memory >> + wildmatch test: perform all tests under all wildmatch() modes >> + wildmatch test: remove dead fnmatch() test code >> + wildmatch test: use a paranoia pattern from nul_match() >> + wildmatch test: don't try to vertically align our output >> + wildmatch test: use more standard shell style >> + wildmatch test: indent with tabs, not spaces >> >> More tests for wildmatch functions. >> >> Will cook in 'next'. > > Please don't merge it down for now. Oops, the above entry in the "What's cooking" report is totally bogus. It is not merged to 'next' yet, and 09f0b84098 does not exist in the public history of the project. What happened was that I rewound 'next' after making a trial merge before pushing the result out. I updated the "What's cooking" report while the trial merge was in 'next', which I should have redone. >> * ab/perf-grep-threads (2018-01-04) 1 commit >> (merged to 'next' on 2018-01-09 at 8fe1d71894) >> + perf: amend the grep tests to test grep.threads >> >> More perf tests for threaded grep >> >> Will cook in 'next'. > > Re: the concern raised in email@example.com I > think it makes sense to just document (and I can do that if you agree) > that: > > test_expect_success SOME_PREREQ,$SOME_OTHER_PREREQ,$ANOTHER_ONE [...] > > Will work as far as prereqs goes even though the variables might be > empty. It's much less verbose than the proposed alternative, and easy to > support. OK. >> Will [cook in|merge to] 'next'. > > Refresh my memory, that means merge down post-2.16.0 at this point, > right? After -rc1, anything merged to 'next' will by default stay there until the final. Hotfixes will be merged to 'next' and (unless I forget) will be marked as "will merge to 'master'" when that happens, so that we will have them in the final.
next prev parent reply index Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-01-09 23:33 Junio C Hamano 2018-01-10 7:56 ` Ævar Arnfjörð Bjarmason 2018-01-10 20:02 ` Junio C Hamano [this message] 2018-01-10 16:25 ` Jeff Hostetler 2018-01-10 19:57 ` Junio C Hamano 2018-01-10 22:03 ` Jeff Hostetler 2018-01-18 8:56 ` Christian Couder 2018-01-18 22:31 ` Jonathan Tan
Reply instructions: You may reply publically 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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
firstname.lastname@example.org mailing list mirror (one of many) Archives are clonable: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git nntp://news.gmane.org/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ or Tor2web: https://www.tor2web.org/ AGPL code for this site: git clone https://public-inbox.org/ public-inbox