git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Johannes Sixt <J.Sixt@eudaptics.com>
Cc: git@vger.kernel.org
Subject: [PATCH] git add: respect core.filemode even with unmerged entries in the index
Date: Thu, 28 Jun 2007 18:02:21 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706281653260.4438@racer.site> (raw)
In-Reply-To: <4683CA7A.7F8070D7@eudaptics.com>


When a merge left unmerged entries, git add failed to pick up the
file mode from the index, when core.filemode == 0.

Noticed by Johannes Sixt.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
---

	On Thu, 28 Jun 2007, Johannes Sixt wrote:

	> Johannes Sixt wrote:
	> 
	> The deficiency is not in merge-recursive, but in 'git add'. The 
	> problem is that after a conflicted merge of an executable file 
	> 'git add' loses the +x bit even if core.filemode=false.

	How's that?

 read-cache.c   |    6 ++++++
 t/t3700-add.sh |   14 ++++++++++++++
 2 files changed, 20 insertions(+), 0 deletions(-)

diff --git a/read-cache.c b/read-cache.c
index 4362b11..a74e4a7 100644
--- a/read-cache.c
+++ b/read-cache.c
@@ -382,6 +382,12 @@ int add_file_to_index(struct index_state *istate, const char *path, int verbose)
 		struct cache_entry *ent;
 		int pos = index_name_pos(istate, path, namelen);
 
+		/* might be unmerged */
+		if (pos < 0 && 1-pos < istate->cache_nr &&
+				namelen == ce_namelen(istate->cache[1-pos]) &&
+				!memcmp(path, istate->cache[1-pos]->name,
+					namelen))
+			pos = 1-pos;
 		ent = (0 <= pos) ? istate->cache[pos] : NULL;
 		ce->ce_mode = ce_mode_from_stat(ent, st.st_mode);
 	}
diff --git a/t/t3700-add.sh b/t/t3700-add.sh
index ad8cc7d..d75970b 100755
--- a/t/t3700-add.sh
+++ b/t/t3700-add.sh
@@ -110,4 +110,18 @@ test_expect_success 'check correct prefix detection' '
 	git add 1/2/a 1/3/b 1/2/c
 '
 
+test_expect_success 'git add and filemode=0 with unmerged entries' '
+	echo 1 > stage1 &&
+	echo 2 > stage2 &&
+	echo 3 > stage3 &&
+	for s in 1 2 3
+	do
+		echo "100755 $(git hash-object -w stage$s) $s	file"
+	done | git update-index --index-info &&
+	git config core.filemode 0 &&
+	echo new > file &&
+	git add file &&
+	git ls-files --stage | grep "^100755 .* 0	file$"
+'
+
 test_done
-- 
1.5.2.2.3228.g16a27

  reply	other threads:[~2007-06-28 17:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25  6:40 most commonly used git commands? Michael S. Tsirkin
2007-06-25  7:10 ` Junio C Hamano
2007-06-25  7:17   ` Michael S. Tsirkin
2007-06-25  7:48     ` Junio C Hamano
2007-06-28  2:17       ` Martin Langhoff
2007-06-28  2:30         ` Josh Triplett
2007-06-25  7:51     ` Johannes Schindelin
2007-06-28  8:52       ` Alex Riesen
2007-06-28 13:08         ` Johannes Schindelin
2007-06-28 13:54           ` Johannes Sixt
2007-06-28 14:07             ` Johannes Schindelin
2007-06-28 14:29               ` Johannes Sixt
2007-06-28 14:49                 ` Johannes Sixt
2007-06-28 17:02                   ` Johannes Schindelin [this message]
2007-06-29  6:57                     ` [PATCH] git add: respect core.filemode even with unmerged entriesin the index Johannes Sixt
2007-06-29 10:07                       ` Johannes Schindelin
2007-06-29 10:20                         ` Junio C Hamano
2007-06-29 17:32                           ` [PATCH] git add: respect core.filemode with unmerged entries Johannes Schindelin
2007-06-29  8:36                     ` [PATCH] git add: respect core.filemode even with unmerged entries in the index Junio C Hamano
2007-06-29 10:06                       ` Johannes Schindelin
2007-06-30 13:14               ` most commonly used git commands? Alex Riesen
2007-06-30 14:31                 ` Johannes Schindelin
2007-06-30 22:35                   ` Alex Riesen
2007-07-01  9:16                     ` Jan Hudec
2007-07-01 16:49                       ` Alex Riesen
2007-06-28  1:37 ` Josh Triplett

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=Pine.LNX.4.64.0706281653260.4438@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=J.Sixt@eudaptics.com \
    --cc=git@vger.kernel.org \
    /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).