delta/git.git/t/t5505-remote.sh, branch sg/lock-file-commit-error

t: fix some trivial cases of ignored exit codes in loops

2015-03-25T17:25:27+00:00

These are all cases where we do a setup step of the form:

  for i in $foo; do
	  set_up $i || break
  done &&
  more_setup

would not notice a failure in set_up (because break always
returns a 0 exit code). These are just setup steps that we
do not expect to fail, but it does not hurt to be defensive.

Most can be fixed by converting the "break" to a "return 1"
(since we eval our tests inside a function for just this
purpose). A few of the loops are inside subshells, so we can
use just "exit 1" to break out of the subshell. And a few
can actually be made shorter by just unrolling the loop.

Signed-off-by: Jeff King 
Signed-off-by: Junio C Hamano

Add a regression test for 'git remote add '

2014-12-23T20:42:37+00:00

Signed-off-by: Johannes Schindelin 
Signed-off-by: Junio C Hamano

connect: annotate refs with their symref information in get_remote_head()

2013-09-18T04:58:46+00:00

By doing this, clients of upload-pack can now reliably tell what ref
a symbolic ref points at; the updated test in t5505 used to expect
failure due to the ambiguity and made sure we give diagnostics, but
we no longer need to be so pessimistic. Make sure we correctly learn
which branch HEAD points at from the other side instead.

Signed-off-by: Junio C Hamano

t5505: fix "set-head --auto with ambiguous HEAD" test

2013-09-18T04:45:34+00:00

When two or more branches point at the same commit and HEAD is
pointing at one of them, without the symref extension, there is no
way to remotely tell which one of these branches HEAD points at.
The test in question attempts to make sure that this situation is
diagnosed and results in a failure.

However, even if there _were_ a way to reliably tell which branch
the HEAD points at, "set-head --auto" would fail if there is no
remote tracking branch.  Make sure that this test does not fail
for that "wrong" reason.

Signed-off-by: Junio C Hamano

Merge branch 'ms/remote-tracking-branches-in-doc'

2013-07-12T19:04:07+00:00

* ms/remote-tracking-branches-in-doc:
  Change "remote tracking" to "remote-tracking"

Change "remote tracking" to "remote-tracking"

2013-07-03T20:27:15+00:00

Fix a typo ("remote remote-tracking") going back to the big cleanup
in 2010 (8b3f3f84 etc). Also, remove some more occurrences of
"tracking" and "remote tracking" in favor of "remote-tracking".

Signed-off-by: Michael Schubert 
Reviewed-by: Johan Herland 
Signed-off-by: Junio C Hamano

t/t5505-remote: test multiple push/pull in remotes-file

2013-06-23T07:33:58+00:00

Extend the test "migrate a remote from named file in $GIT_DIR/remotes"
to test that multiple "Push:" and "Pull:" lines in the remotes-file
works as expected.

Signed-off-by: Ramkumar Ramachandra 
Signed-off-by: Junio C Hamano

t/t5505-remote: test url-with-# in branches-file

2013-06-23T07:33:57+00:00

Add one more test similar to "migrate a remote from named file in
$GIT_DIR/branches" to check that a url with a # can be used to specify
the branch name (as opposed to the constant "master").

Signed-off-by: Ramkumar Ramachandra 
Signed-off-by: Junio C Hamano

t/t5505-remote: use test_path_is_missing

2013-06-23T07:14:33+00:00

Replace instances of ! test -f with test_path_is_missing.

Signed-off-by: Ramkumar Ramachandra 
Signed-off-by: Junio C Hamano

t/t5505-remote: test push-refspec in branches-file

2013-06-23T07:14:15+00:00

The test "migrate a remote from named file in $GIT_DIR/branches" reads
the branches-file, but only checks that the url and fetch-refspec are
set correctly.  Check that the push-refspec is also set correctly.

Signed-off-by: Ramkumar Ramachandra 
Signed-off-by: Junio C Hamano