From: Jakub Narebski <jnareb@gmail.com>
To: "Ray Chuan" <rctay89@gmail.com>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org
Subject: Re: [PATCH 3/3] http-push: update tests
Date: Sat, 17 Jan 2009 12:21:37 -0800 (PST) [thread overview]
Message-ID: <m3zlhpy981.fsf@localhost.localdomain> (raw)
In-Reply-To: <be6fef0d0901171155p26e14aa1t90c0d7b8ec7925f3@mail.gmail.com>
"Ray Chuan" <rctay89@gmail.com> writes:
>>>>> - 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.
Errr...
git push &&
[ -f "$HTTPD_DOCUMENT_ROOT_PATH/test_repo.git/refs/heads/master" ]
means, do "git push", and if it succeeds test (which should really be
written as 'test <cond>' and not '[ <cond> ]' I think) if the file
does exists and is regular file ('help test' or 'man test').
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-01-17 20:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-17 2:59 [PATCH 3/3] http-push: update tests Ray Chuan
2009-01-17 5:23 ` Johannes Schindelin
2009-01-17 8:40 ` Ray Chuan
2009-01-17 18:54 ` Junio C Hamano
2009-01-17 19:37 ` Johannes Schindelin
2009-01-17 19:55 ` Ray Chuan
2009-01-17 20:21 ` Jakub Narebski [this message]
2009-01-17 21:00 ` Ray Chuan
2009-01-17 21:15 ` Jakub Narebski
2009-01-17 21:24 ` Johannes Schindelin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zlhpy981.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rctay89@gmail.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).