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

Re: [PATCH 3/3] http-push: update tests

From
Ray Chuan <rctay89@gmail.com>
Date
Jan 17, 2009, 19:55 UTC
Message-ID
<be6fef0d0901171155p26e14aa1t90c0d7b8ec7925f3@mail.gmail.com>
In-Reply-To
<7vsknh7og5.fsf@gitster.siamese.dyndns.org>
Hi,
On Sat, Jan 17, 2009 at 6:54 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 11 quoted lines
> "Ray Chuan" <rctay89@gmail.com> writes:
>
>>>> -test_expect_failure 'push to remote repository' '
>>>> +test_expect_success 'push to remote repository' '
>>>>       cd "$ROOT_PATH"/test_repo_clone &&
>>>>       : >path2 &&
>>>>       git add path2 &&
>>>>       test_tick &&
>>>>       git commit -m path2 &&
>>>> -     git push &&
>>>> -     [ -f "$HTTPD_DOCUMENT_ROOT_PATH/test_repo.git/refs/heads/master" ]

i modified the push arguments as there was no remote ref/branch specified. With a fixed "git push", that line says:

  No refs in common and none specified; doing nothing.

i'd like to take this chance to inquire, what does the -f, plus square brackets, really mean? i assumed it was to force push to go ahead even if "a remote ref that is not an ancestor of the local ref used to overwrite it" check fails.

-- 
Cheers,
Ray Chuan
Previous: Johannes SchindelinNext: Jakub Narebski
Message 6 of 10 in “http-push: update tests”
  1. 3/3 http-push: update testsRay Chuan, Jan 17, 2009
  2. Johannes SchindelinJan 17, 2009
  3. Ray ChuanJan 17, 2009
  4. Junio C HamanoJan 17, 2009
  5. Johannes SchindelinJan 17, 2009
  6. Ray ChuanJan 17, 2009
  7. Jakub NarebskiJan 17, 2009
  8. Ray ChuanJan 17, 2009
  9. Jakub NarebskiJan 17, 2009
  10. Johannes SchindelinJan 17, 2009

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.