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

Re: [RFC PATCH 0/2] Fix unnecessary updates of files during merge

From
Elijah Newren <newren@gmail.com>
Date
Feb 26, 2011, 18:43 UTC
Message-ID
<AANLkTiknGZ-WQrwhtX9rJ=k1z7p3cYCE-j8F7rt4UL+M@mail.gmail.com>
In-Reply-To
<1298745297-25713-1-git-send-email-newren@gmail.com>
Hi,
On Sat, Feb 26, 2011 at 11:34 AM, Elijah Newren <newren@gmail.com> wrote:
Show 8 quoted lines
> This patch series adds a simple testcase demonstrating the problem
> reported by Stephen Rothwell, and a fix.  Unfortunately, there's a bug
> with the fix (hence the RFC) that makes the relevant files racily clean
> rather than clearly clean (i.e. 'git diff-files' will report these files
> as modified when it shouldn't).
>
> I'll try to figure out how to fix the second problem in the next few
> days.  If anyone has some hints, I'm all ears.
And, of course, I forgot to include the cc's in my send-email command.
 Sorry about that, Stephen and Jeff.  Adding you on this email, at
least.
Show 9 quoted lines
> Elijah Newren (2):
>  t6022: New test checking for unnecessary updates of renamed+modified
>    files
>  merge-recursive: When we detect we can skip an update, actually skip
>    it
>
>  merge-recursive.c       |    7 +++++--
>  t/t6022-merge-rename.sh |   32 ++++++++++++++++++++++++++++++++
>  2 files changed, 37 insertions(+), 2 deletions(-)
Previous: Elijah Newren
Message 8 of 8 in “new behaviour in git merge”
  1. Stephen RothwellFeb 24, 2011
  2. Jeff KingFeb 24, 2011
  3. Stephen RothwellFeb 24, 2011
  4. Jeff KingFeb 24, 2011
  5. 0/2 Fix unnecessary updates of files during mergeElijah Newren, Feb 26, 2011
  6. 1/2 t6022: New test checking for unnecessary updates of renamed+modified filesElijah Newren, Feb 26, 2011
  7. 2/2 merge-recursive: When we detect we can skip an update, actually skip itElijah Newren, Feb 26, 2011
  8. Elijah NewrenFeb 26, 2011

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.