Re: [PATCH v4 2/5] name-rev: extend --refs to accept multiple patterns
- From
Jacob Keller <jacob.keller@gmail.com>
- Date
- Jan 19, 2017, 23:36 UTC
- Message-ID
- <CA+P7+xokEvYo4as5w0O5SbS6KE86fO=a7VnR_JroTOHebWSayw@mail.gmail.com>
- In-Reply-To
- <xmqqfukezrmh.fsf@gitster.mtv.corp.google.com>
On Thu, Jan 19, 2017 at 1:06 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 23 quoted lines
> Jacob Keller <jacob.e.keller@intel.com> writes: > >> From: Jacob Keller <jacob.keller@gmail.com> >> >> Teach git name-rev to take multiple --refs stored as a string list of >> patterns. The list of patterns will be matched inclusively, and each ref >> only needs to match one pattern to be included. A ref will only be >> excluded if it does not match any of the given patterns. Additionally, >> if any of the patterns would allow abbreviation, then we will abbreviate >> the ref, even if another pattern is more strict and would not have >> allowed abbreviation on its own. >> >> Add tests and documentation for this change. The tests expected output >> is dynamically generated, but this is in order to avoid hard-coding >> a commit object id in the test results (as the expected output is to >> simply leave the commit object unnamed). > > Makes sense. > > I do not see anything that requires "... generated, but" there, > though, as if it is a bad thing to do to prepare expected output > dynamically. I'd just reword "generated. This is..." to make it > neutral.
Makes sense. I was commenting this way since I was requested that someone on the list preferred non-dynamic test expectations.
Thanks, Jake