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

Re: [PATCH] git-checkout: Test for relative path use.

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 9, 2007, 09:06 UTC
Message-ID
<7vfxzfvlch.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<ee77f5c20711090014qfed56e7y446c014399e47a82@mail.gmail.com>
"David Symonds" <dsymonds@gmail.com> writes:
> So what would you prefer? Bracketing the whole test in parentheses
> looks ugly, but I can do that if that's the only option. If I look at
> t5510-fetch.sh (one of yours, Junio), there is no directory
> restoration in the case of test failure, as in my original patch.

Yes, that is what I was referring to as "bad examples". The way t4116 goes down to different directory do not look ugly to me.

Previous: David SymondsNext: David Symonds
Message 13 of 15 in “git-checkout: Support relative paths containing "..".”
  1. git-checkout: Support relative paths containing "..".David Symonds, Nov 9, 2007
  2. git-checkout: Test for relative path use.David Symonds, Nov 9, 2007
  3. Junio C HamanoNov 9, 2007
  4. David SymondsNov 9, 2007
  5. Junio C HamanoNov 9, 2007
  6. David SymondsNov 9, 2007
  7. Robin RosenbergNov 9, 2007
  8. Johannes SixtNov 9, 2007
  9. David SymondsNov 9, 2007
  10. git-checkout: Test for relative path use.David Symonds, Nov 9, 2007
  11. Junio C HamanoNov 9, 2007
  12. David SymondsNov 9, 2007
  13. Junio C HamanoNov 9, 2007
  14. David SymondsNov 9, 2007
  15. git-checkout: Test for relative path use.David Symonds, Nov 9, 2007

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.