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

Re: [PATCH] rerere: record (or avoid misrecording) resolved, skipped or aborted rebase/am

From
Jakub Narebski <jnareb@gmail.com>
Date
Dec 8, 2006, 21:44 UTC
Message-ID
<elcm6u$l8t$1@sea.gmane.org>
In-Reply-To
<1165613397460-git-send-email-normalperson@yhbt.net>
Eric Wong wrote:
Just one comment:
Show 15 quoted lines
> +       if test -d "$GIT_DIR/rr-cache"
> +       then
> +               git-rerere clear
> +       fi
>         this=`expr "$this" + 1`
>         resume=
>  fi
> @@ -408,6 +412,10 @@ do
>                         stop_here_user_resolve $this
>                 fi
>                 apply_status=0
> +               if test -d "$GIT_DIR/rr-cache"
> +               then
> +                       git rerere
> +               fi

Why do you use once "git-rerere", and another time "git rerere"? Shouldn't scripts always use git-command form?

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Eric WongNext: Eric Wong
Message 5 of 7 in “Re: [PATCH 1/5] rerere: avoid misrecording on a skipped or aborted rebase/am”
  1. Junio C HamanoDec 8, 2006
  2. Eric WongDec 8, 2006
  3. rerere: add clear, diff, and status commandsEric Wong, Dec 8, 2006
  4. rerere: record (or avoid misrecording) resolved, skipped or aborted rebase/amEric Wong, Dec 8, 2006
  5. Jakub NarebskiDec 8, 2006
  6. Eric WongDec 8, 2006
  7. Junio C HamanoDec 9, 2006

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.