git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elijah Newren <newren@gmail.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>,
	Jeff King <peff@peff.net>, Elijah Newren <newren@gmail.com>
Subject: [PATCHv3 0/3] Fix unnecessary (mtime) updates of files during merge
Date: Wed,  2 Mar 2011 23:13:09 -0700	[thread overview]
Message-ID: <1299132792-17497-1-git-send-email-newren@gmail.com> (raw)

This patch series fixes a bug reported by Stephen Rothwell -- that
during merges git would unnecessarily update modification times of
files.  As noted by both Jeff and Junio, it's a bit of a band-aid
since it doesn't dive into fixing make_room_for_path() and
make_room_for_directories_of_df_conflicts(), but that would be a
much bigger and more invasive change.

Changes since last version:
  * Portability fixes for the tests suggested by Hannes (thanks!)
  * Additional test cleanups suggested by Jeff
  * Jeff's acks have been added

Elijah Newren (3):
  t6022: New test checking for unnecessary updates of renamed+modified files
  t6022: New test checking for unnecessary updates of files in D/F conflicts
  merge-recursive: When we detect we can skip an update, actually skip it

 merge-recursive.c       |   17 ++++++++----
 t/t6022-merge-rename.sh |   65 +++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 76 insertions(+), 6 deletions(-)

-- 
1.7.4

             reply	other threads:[~2011-03-03  6:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-03  6:13 Elijah Newren [this message]
2011-03-03  6:13 ` [PATCHv3 1/3] t6022: New test checking for unnecessary updates of renamed+modified files Elijah Newren
2011-03-03  6:13 ` [PATCHv3 2/3] t6022: New test checking for unnecessary updates of files in D/F conflicts Elijah Newren
2011-03-03  6:13 ` [PATCHv3 3/3] merge-recursive: When we detect we can skip an update, actually skip it Elijah Newren
2011-03-03 17:52 ` [PATCHv3 0/3] Fix unnecessary (mtime) updates of files during merge Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1299132792-17497-1-git-send-email-newren@gmail.com \
    --to=newren@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).