git-commit-vandalism/t/t5515/refs.master_.._.git_one_two

0567da4d5edd2ff4bb292a465ba9e64dcad9536b refs/remotes/origin/HEAD
754b754407bf032e9a2f9d5a9ad05ca79a6b228f refs/remotes/origin/master
8e32a6d901327a23ef831511badce7bf3bf46689 refs/remotes/origin/one
0567da4d5edd2ff4bb292a465ba9e64dcad9536b refs/remotes/origin/three
6134ee8f857693b96ff1cc98d3e2fd62b199e5a8 refs/remotes/origin/two
git-fetch test: test tracking fetch results, not just FETCH_HEAD We really should have done this long time ago. Existing t5515 test was written for the specific purpose of catching regression to the contents of generated FETCH_HEAD file, but it also is a good place to make sure various fetch configurations do fetch what they intend to fetch (and nothing else). Signed-off-by: Junio C Hamano <gitster@pobox.com> 2008-03-26 09:17:07 +01:00			`0567da4d5edd2ff4bb292a465ba9e64dcad9536b refs/remotes/origin/HEAD`
			`754b754407bf032e9a2f9d5a9ad05ca79a6b228f refs/remotes/origin/master`
			`8e32a6d901327a23ef831511badce7bf3bf46689 refs/remotes/origin/one`
			`0567da4d5edd2ff4bb292a465ba9e64dcad9536b refs/remotes/origin/three`
			`6134ee8f857693b96ff1cc98d3e2fd62b199e5a8 refs/remotes/origin/two`