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

Re: [PATCH v3 3/3] cat-file: add --follow-symlinks to --batch

From
David Turner <dturner@twopensource.com>
Date
May 11, 2015, 17:03 UTC
Message-ID
<1431363819.15048.2.camel@ubuntu>
In-Reply-To
<554F0378.2070803@kdbg.org>
On Sun, 2015-05-10 at 09:06 +0200, Johannes Sixt wrote:
Show 11 quoted lines
> > +	ln -s loop2 loop1 &&
> > +	git add . &&
> > +	git commit -am "test"
> > +'
> 
> These tests will fail on a file system that does not support symbolic 
> links, such as on Windows. Would you please separate the test cases 
> (that come after the setup) into two groups:
> 
> 1. Those that inspect the filesystem and expect a symbolic link. Protect 
> these tests with a SYMLINKS prerequisite.
I believe that none of these require that.
> Note that you do not require a symlink enabled file system to generate a 
> repository with symlinks, i.e., you don't have to protect the setup code 
> with SYMLINKS. For this, you can use 'test_ln_s_add' instead of the 
> above sequence of 'ln -s' followed by a single 'git add .'.
Will fix, thanks.
Show 5 quoted lines
> > +
> > +echo $hello_sha1 blob $hello_size > found
> 
> This seems to be used only in the next test. Please move it inside 
> test_expect_success.
This is used in a number of tests, e.g this one:
> > +test_expect_success 'git cat-file --batch-check --follow-symlinks works for in-repo, same-dir links' '
> > +	echo HEAD:same-dir-link | git cat-file --batch-check --follow-symlinks > actual &&
> > +	test_cmp found actual
> > +'
Previous: Johannes SixtNext: Junio C Hamano
Message 6 of 8 in “tree-walk: learn get_tree_entry_follow_symlinks”
  1. 1/3 tree-walk: learn get_tree_entry_follow_symlinksdturner@twopensource.com, May 9, 2015
  2. 2/3 sha1_name: get_sha1_with_context learns to follow symlinksdturner@twopensource.com, May 9, 2015
  3. Junio C HamanoMay 10, 2015
  4. 3/3 cat-file: add --follow-symlinks to --batchdturner@twopensource.com, May 9, 2015
  5. Johannes SixtMay 10, 2015
  6. David TurnerMay 11, 2015
  7. Junio C HamanoMay 11, 2015
  8. Junio C HamanoMay 10, 2015

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.