git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/6] transport-helper: clarify *:* refspec

From
Thomas Rast <trast@inf.ethz.ch>
Date
Apr 18, 2013, 12:39 UTC
Message-ID
<87ppxsvwq7.fsf@linux-k42r.v.cablecom.net>
In-Reply-To
<CAMP44s0c-c3pPW8t9p9qabjv46gSeE6y4p6STPeV+kqB77xOJA@mail.gmail.com>
Felipe Contreras <felipe.contreras@gmail.com> writes:
Show 32 quoted lines
> On Thu, Apr 18, 2013 at 2:28 AM, Thomas Rast <trast@inf.ethz.ch> wrote:
>> Felipe Contreras <felipe.contreras@gmail.com> writes:
>>
>>> The *:* refspec doesn't work, and never has, clarify the code and
>>> documentation to reflect that. This in effect reverts commit 9e7673e
>>> (gitremote-helpers(1): clarify refspec behaviour).
>> [...]
>>> -test_expect_success 'pulling with straight refspec' '
>>> -     (cd local2 &&
>>> -     GIT_REMOTE_TESTGIT_REFSPEC="*:*" git pull) &&
>>> -     compare_refs local2 HEAD server HEAD
>>> -'
>>> -
>>> -test_expect_failure 'pushing with straight refspec' '
>>> -     test_when_finished "(cd local2 && git reset --hard origin)" &&
>>> -     (cd local2 &&
>>> -     echo content >>file &&
>>> -     git commit -a -m eleven &&
>>> -     GIT_REMOTE_TESTGIT_REFSPEC="*:*" git push) &&
>>> -     compare_refs local2 HEAD server HEAD
>>> -'
>>
>> So what's wrong with the tests?  Do they fail to test what they claim
>> (how?), test something that wasn't reasonable to begin with, or
>> something entirely different?
>
> Look at the code comment, and look at the now updated documentation
> that assumes that *:* was reasonable. Given the available information,
> it would be reasonable to assume that *:* did work, but it didn't
> work, and it's not really possible to fix it, even if we wanted to, it
> would be a hack. It's better to accept that fact and stop worrying too
> much about what would be the best way to do the wrong thing.

Ok, you say that the *failing* test set an expectation that is unrealistic, so let's drop it.

But then what about the successful test? Does it actually work (and by removing the test, you are saying that we don't care if we subsequently break that (mis)feature)? Or did it test the wrong thing?

-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Felipe ContrerasNext: Felipe Contreras
Message 5 of 14 in “transport-helper: some clarifications and a fix”
  1. 0/6 transport-helper: some clarifications and a fixFelipe Contreras, Apr 18, 2013
  2. 1/6 transport-helper: clarify *:* refspecFelipe Contreras, Apr 18, 2013
  3. Thomas RastApr 18, 2013
  4. Felipe ContrerasApr 18, 2013
  5. Thomas RastApr 18, 2013
  6. Felipe ContrerasApr 18, 2013
  7. 2/6 transport-helper: update refspec documentationFelipe Contreras, Apr 18, 2013
  8. 3/6 transport-helper: clarify pushing without refspecsFelipe Contreras, Apr 18, 2013
  9. Sverre RabbelierApr 18, 2013
  10. Stefano LattariniApr 18, 2013
  11. 4/6 transport-helper: warn when refspec is not usedFelipe Contreras, Apr 18, 2013
  12. 5/6 transport-helper: trivial code shuffleFelipe Contreras, Apr 18, 2013
  13. 6/6 transport-helper: update remote helper namespaceFelipe Contreras, Apr 18, 2013
  14. Felipe ContrerasApr 18, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.