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

Re: [PATCH v3 1/3] worktree: refactor infer_backlink() to use *strbuf

From
shejialuo <shejialuo@gmail.com>
Date
Oct 10, 2024, 15:52 UTC
Message-ID
<Zwf4PT-vaLX35ELL@ArchLinux>
In-Reply-To
<20241007-wt_relative_paths-v3-1-622cf18c45eb@pm.me>
On Mon, Oct 07, 2024 at 10:12:30PM -0500, Caleb White via B4 Relay wrote:
Show 6 quoted lines
> From: Caleb White <cdwhite3@pm.me>
> 
> This lays the groundwork for the next patch, which needs the backlink
> returned from infer_backlink() as a `strbuf`. It seemed inefficient to
> convert from `strbuf` to `char*` and back to `strbuf` again.
> 

I think here we should first talk about the current behavior of the `infer_backlink`:

    `infer_backlink` initializes a "strbuf" for the inferred backlink
    and returns the result with type "char *" by detaching the "strbuf"

And then you should tell your intention like the following (The reader like me does not know what is the intention of the next patch, you should __explicitly__ mention this).

    Because we decide to link worktrees with relative paths, we need to
    convert the returned inferred backlink "char *" to "strbuf".
    However, it is a bad idea to convert from `strbuf` to `char*` and
    back to `strbuf` again. Instead, we should just let the
    `infer_backlink` to accept the "struct strbuf *" parameter to
    improve efficiency.
> This refactors infer_backlink() to return an integer result and use a
> pre-allocated `strbuf` for the inferred backlink path, replacing the
> previous `char*` return type and improving efficiency.
> 

I think you should also talk about that you make the `repair_worktree_at_path` function to align with above refactor.

Show 28 quoted lines
> Signed-off-by: Caleb White <cdwhite3@pm.me>
> ---
>  worktree.c | 48 ++++++++++++++++++++++++------------------------
>  1 file changed, 24 insertions(+), 24 deletions(-)
> 
> diff --git a/worktree.c b/worktree.c
> index ec95ea2986107b3bc12d38b0825d7c6e87402bc6..0cba0d6e6e9ad02ace04a0301104a04a07cbef65 100644
> --- a/worktree.c
> +++ b/worktree.c
> @@ -642,10 +642,9 @@ static int is_main_worktree_path(const char *path)
>   * be able to infer the gitdir by manually reading /path/to/worktree/.git,
>   * extracting the <id>, and checking if <repo>/worktrees/<id> exists.
>   */
> -static char *infer_backlink(const char *gitfile)
> +static int infer_backlink(const char *gitfile, struct strbuf *inferred)
>  {
>  	struct strbuf actual = STRBUF_INIT;
> -	struct strbuf inferred = STRBUF_INIT;
>  	const char *id;
>  
>  	if (strbuf_read_file(&actual, gitfile, 0) < 0)
> @@ -658,17 +657,18 @@ static char *infer_backlink(const char *gitfile)
>  	id++; /* advance past '/' to point at <id> */
>  	if (!*id)
>  		goto error;
> -	strbuf_git_common_path(&inferred, the_repository, "worktrees/%s", id);
> -	if (!is_directory(inferred.buf))
> +	strbuf_reset(inferred);

Question here: should we use `strbuf_reset` here? I want to know the reason why you design this. Is the caller's responsibility to clear the "inferred" when calling this function?

Show 15 quoted lines
> +	strbuf_git_common_path(inferred, the_repository, "worktrees/%s", id);
> +	if (!is_directory(inferred->buf))
>  		goto error;
>  
>  	strbuf_release(&actual);
> -	return strbuf_detach(&inferred, NULL);
> +	return 1;
>  
>  error:
>  	strbuf_release(&actual);
> -	strbuf_release(&inferred);
> -	return NULL;
> +	strbuf_reset(inferred); /* clear invalid path */
> +	return 0;
>  }

Design question, when calling `infer_backlink` successfully, we will return 1, if not, we will return 0. But in the later code, we use the "inferred.buf.len" to indicate whether we could get the inferred backlink successfully.

We have two signals to indicate the success. I think it's a bad idea to use "inferred.buf.len". Let me give you an example here:

    struct strbuf inferred_backlink = STRBUF_INIT;
    inferred_backlink = infer_backlink(realdotgit.buf);
    // What if I wrongly use the following statements?
    strbuf_addstr(&inferred_backlink, "foo");
    if (inferred_backlink.buf.len) {
    }

If you insist using "inferred_backlink.buf.len" as the result, this function should return `void`. And you should add some comments for this function.

Show 59 quoted lines
>  
>  /*
> @@ -680,10 +680,11 @@ void repair_worktree_at_path(const char *path,
>  {
>  	struct strbuf dotgit = STRBUF_INIT;
>  	struct strbuf realdotgit = STRBUF_INIT;
> +	struct strbuf backlink = STRBUF_INIT;
> +	struct strbuf inferred_backlink = STRBUF_INIT;
>  	struct strbuf gitdir = STRBUF_INIT;
>  	struct strbuf olddotgit = STRBUF_INIT;
> -	char *backlink = NULL;
> -	char *inferred_backlink = NULL;
> +	char *dotgit_contents = NULL;
>  	const char *repair = NULL;
>  	int err;
>  
> @@ -699,23 +700,23 @@ void repair_worktree_at_path(const char *path,
>  		goto done;
>  	}
>  
> -	inferred_backlink = infer_backlink(realdotgit.buf);
> -	backlink = xstrdup_or_null(read_gitfile_gently(realdotgit.buf, &err));
> -	if (err == READ_GITFILE_ERR_NOT_A_FILE) {
> +	infer_backlink(realdotgit.buf, &inferred_backlink);
> +	dotgit_contents = xstrdup_or_null(read_gitfile_gently(realdotgit.buf, &err));
> +	if (dotgit_contents) {
> +		strbuf_addstr(&backlink, dotgit_contents);
> +	} else if (err == READ_GITFILE_ERR_NOT_A_FILE) {
>  		fn(1, realdotgit.buf, _("unable to locate repository; .git is not a file"), cb_data);
>  		goto done;
>  	} else if (err == READ_GITFILE_ERR_NOT_A_REPO) {
> -		if (inferred_backlink) {
> +		if (inferred_backlink.len) {
>  			/*
>  			 * Worktree's .git file does not point at a repository
>  			 * but we found a .git/worktrees/<id> in this
>  			 * repository with the same <id> as recorded in the
>  			 * worktree's .git file so make the worktree point at
> -			 * the discovered .git/worktrees/<id>. (Note: backlink
> -			 * is already NULL, so no need to free it first.)
> +			 * the discovered .git/worktrees/<id>.
>  			 */
> -			backlink = inferred_backlink;
> -			inferred_backlink = NULL;
> +			strbuf_swap(&backlink, &inferred_backlink);
>  		} else {
>  			fn(1, realdotgit.buf, _("unable to locate repository; .git file does not reference a repository"), cb_data);
>  			goto done;
> @@ -743,13 +744,11 @@ void repair_worktree_at_path(const char *path,
>  	 * in the "copy" repository. In this case, point the "copy" worktree's
>  	 * .git file at the "copy" repository.
>  	 */
> -	if (inferred_backlink && fspathcmp(backlink, inferred_backlink)) {
> -		free(backlink);
> -		backlink = inferred_backlink;
> -		inferred_backlink = NULL;
> +	if (inferred_backlink.len && fspathcmp(backlink.buf, inferred_backlink.buf)) {
> +		strbuf_swap(&backlink, &inferred_backlink);
>  	}
For single line statement after "if", we should not use `{`.
Show 24 quoted lines
>  
> -	strbuf_addf(&gitdir, "%s/gitdir", backlink);
> +	strbuf_addf(&gitdir, "%s/gitdir", backlink.buf);
>  	if (strbuf_read_file(&olddotgit, gitdir.buf, 0) < 0)
>  		repair = _("gitdir unreadable");
>  	else {
> @@ -763,9 +762,10 @@ void repair_worktree_at_path(const char *path,
>  		write_file(gitdir.buf, "%s", realdotgit.buf);
>  	}
>  done:
> -	free(backlink);
> -	free(inferred_backlink);
> +	free(dotgit_contents);
>  	strbuf_release(&olddotgit);
> +	strbuf_release(&backlink);
> +	strbuf_release(&inferred_backlink);
>  	strbuf_release(&gitdir);
>  	strbuf_release(&realdotgit);
>  	strbuf_release(&dotgit);
> 
> -- 
> 2.46.2
> 
> 
Sorry, I could not review other patches today (I need to go sleep).

Thanks, Jialuo

Previous: Caleb White via B4 RelayNext: Caleb White
Message 3 of 24 in “Link worktrees with relative paths”
  1. 0/3 Link worktrees with relative pathsCaleb White via B4 Relay, Oct 8, 2024
  2. 1/3 worktree: refactor infer_backlink() to use *strbufCaleb White via B4 Relay, Oct 8, 2024
  3. shejialuoOct 10, 2024
  4. Caleb WhiteOct 10, 2024
  5. shejialuoOct 10, 2024
  6. Caleb WhiteOct 10, 2024
  7. Junio C HamanoOct 10, 2024
  8. Caleb WhiteOct 10, 2024
  9. Junio C HamanoOct 10, 2024
  10. 3/3 worktree: add test for path handling in linked worktreesCaleb White via B4 Relay, Oct 8, 2024
  11. 2/3 worktree: link worktrees with relative pathsCaleb White via B4 Relay, Oct 8, 2024
  12. Junio C HamanoOct 8, 2024
  13. Caleb WhiteOct 9, 2024
  14. Junio C HamanoOct 9, 2024
  15. Caleb WhiteOct 9, 2024
  16. Junio C HamanoOct 9, 2024
  17. Caleb WhiteOct 10, 2024
  18. Caleb WhiteOct 11, 2024
  19. Caleb WhiteOct 22, 2024
  20. Phillip WoodOct 9, 2024
  21. Caleb WhiteOct 9, 2024
  22. Caleb WhiteOct 8, 2024
  23. Junio C HamanoOct 8, 2024
  24. Caleb WhiteOct 8, 2024

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.