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

Re: [PATCH 2/7] t7900: Start testing usability of namespaced remote refs

From
Junio C Hamano <gitster@pobox.com>
Date
May 7, 2013, 01:29 UTC
Message-ID
<7va9o7pogo.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1367711749-8812-3-git-send-email-johan@herland.net>
Johan Herland <johan@herland.net> writes:
Show 8 quoted lines
> +test_expect_success 'work-around "clone" with namespaced remote refs' '
> +	rm -rf client &&
> +	git init client &&
> +	(
> +		cd client &&
> +		git remote add origin ../server &&
> +		git config --unset-all remote.origin.fetch &&
> +		git config --add remote.origin.fetch "+refs/heads/*:refs/remotes/origin/heads/*" &&

If you were to do this, I think you should drop the "remote add origin" step and illustrate what configuration variables should be prepared (at least minimally---the final implementation of "git clone --separate-remote-layout" may add some other configuration variable as a hint to say "this remote is using the new layout" or somesuch) in this "client" repository.

That would make the test more self documenting.

I am not convinced that it is a good idea to reuse "remotes/origin" hierarchy which traditionally has been branches-only like this, though. It may be better to use

	refs/$remotes_new_layout/origin/{heads,tags,...}/*

for a value of $remotes_new_layout that is different from "remote", and teach the dwim_ref() machinery to pay attention to it, to avoid confusion. Otherwise, you wouldn't be able to tell between a topic branch that works on tags named "tags/refactor" under the old layout, and a tag that marks a good point in a refactoring effort "refactor" under the new layout.

Show 11 quoted lines
> +		git config --add remote.origin.fetch "+refs/tags/*:refs/remotes/origin/tags/*" &&
> +		git config --add remote.origin.fetch "+refs/notes/*:refs/remotes/origin/notes/*" &&
> +		git config --add remote.origin.fetch "+refs/replace/*:refs/remotes/origin/replace/*" &&
> +		git config remote.origin.tagopt "--no-tags" &&
> +		git fetch &&
> +		git checkout master
> +	) &&
> +	test_clone client
> +'
> +
> +test_done
Previous: Johan HerlandNext: Johan Herland
Message 15 of 39 in “Make "$remote/$branch" work with unconventional refspecs”
  1. 0/7 Make "$remote/$branch" work with unconventional refspecsJohan Herland, May 4, 2013
  2. 1/7 shorten_unambiguous_ref(): Allow shortening refs/remotes/origin/HEAD to originJohan Herland, May 4, 2013
  3. Bert WesargMay 5, 2013
  4. Junio C HamanoMay 6, 2013
  5. Johan HerlandMay 7, 2013
  6. 1/3 t1514: Add tests of shortening refnames in strict/loose modeJohan Herland, May 7, 2013
  7. 2/3 t1514: Demonstrate failure to correctly shorten "refs/remotes/origin/HEAD"Johan Herland, May 7, 2013
  8. 3/3 shorten_unambiguous_ref(): Fix shortening refs/remotes/origin/HEAD to originJohan Herland, May 7, 2013
  9. Junio C HamanoMay 7, 2013
  10. Junio C HamanoMay 7, 2013
  11. Johan HerlandMay 7, 2013
  12. Junio C HamanoMay 7, 2013
  13. Johan HerlandMay 7, 2013
  14. 2/7 t7900: Start testing usability of namespaced remote refsJohan Herland, May 4, 2013
  15. Junio C HamanoMay 7, 2013
  16. Johan HerlandMay 7, 2013
  17. Junio C HamanoMay 7, 2013
  18. 3/7 t7900: Demonstrate failure to expand "$remote/$branch" according to refspecsJohan Herland, May 4, 2013
  19. Junio C HamanoMay 7, 2013
  20. 4/7 refs.c: Refactor rules for expanding shorthand names into full refnamesJohan Herland, May 4, 2013
  21. Junio C HamanoMay 7, 2013
  22. 5/7 refs.c: Refactor code for shortening full refnames into shorthand namesJohan Herland, May 4, 2013
  23. Junio C HamanoMay 7, 2013
  24. 6/7 refname_match(): Caller must declare if we're matching local or remote refsJohan Herland, May 4, 2013
  25. Junio C HamanoMay 7, 2013
  26. 7/7 refs.c: Add rules for resolving refs using remote refspecsJohan Herland, May 4, 2013
  27. Junio C HamanoMay 5, 2013
  28. Johan HerlandMay 5, 2013
  29. Junio C HamanoMay 5, 2013
  30. Johan HerlandMay 5, 2013
  31. Junio C HamanoMay 5, 2013
  32. Santi BéjarMay 6, 2013
  33. Santi BéjarMay 6, 2013
  34. Junio C HamanoMay 6, 2013
  35. Santi BéjarMay 6, 2013
  36. Junio C HamanoMay 6, 2013
  37. Junio C HamanoMay 6, 2013
  38. Johan HerlandMay 6, 2013
  39. Junio C HamanoMay 7, 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.