git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Han Jiang <jhcarl0814@gmail.com>
To: git@vger.kernel.org
Subject: `git merge --no-overwrite-ignore` overwrites ignored files when merge (i.e. not fast-forward)
Date: Sun, 1 Sep 2024 22:49:05 +1200	[thread overview]
Message-ID: <CANrWfmRvtz=WOPpv54-22aEFsCPi_vwpFo_Q08vq31NjggOVsw@mail.gmail.com> (raw)

Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.

What did you do before the bug happened? (Steps to reproduce your issue)

(`git merge --no-overwrite-ignore` overwrites ignored files when merge
with conflict.)
cd '/'; cd '/'; rm --force --recursive -- './test_git'; mkdir "$_"; cd "$_";
mkdir --parents -- './repo';
git init './repo'
echo '1' >'./repo/file_conflict'; git -C './repo' add
'./file_conflict'; git -C './repo' commit -m "$((++number))"
git -C './repo' branch branch2
git -C './repo' checkout -b branch1; echo 'file' >'./repo/.gitignore';
git -C './repo' add './.gitignore'; echo '2' >'./repo/file_conflict';
git -C './repo' add './file_conflict'; git -C './repo' commit -m
"$((++number))"
git -C './repo' checkout branch2; echo '1' >'./repo/file'; git -C
'./repo' add './file'; echo '3' >'./repo/file_conflict'; git -C
'./repo' add './file_conflict'; git -C './repo' commit -m
"$((++number))"
git -C './repo' checkout branch1
echo '2' >'./repo/file';
git -C './repo' log --graph --all --patch
git -C './repo' status --verbose --verbose
cat './repo/file'
git -C './repo' merge -m "$((++number))" --no-overwrite-ignore branch2
git -C './repo' log --graph --all --patch
git -C './repo' status --verbose --verbose
cat './repo/file'

(`git merge --no-overwrite-ignore` overwrites ignored files when merge
without conflict.)
cd '/'; cd '/'; rm --force --recursive -- './test_git'; mkdir "$_"; cd "$_";
mkdir --parents -- './repo';
git init './repo'
git -C './repo' commit -m "$((++number))" --allow-empty
git -C './repo' branch branch2
git -C './repo' checkout -b branch1; echo 'file' >'./repo/.gitignore';
git -C './repo' add './.gitignore'; git -C './repo' commit -m
"$((++number))"
git -C './repo' checkout branch2; echo '1' >'./repo/file'; git -C
'./repo' add './file'; git -C './repo' commit -m "$((++number))"
git -C './repo' checkout branch1
echo '2' >'./repo/file';
git -C './repo' log --graph --all --patch
git -C './repo' status --verbose --verbose
cat './repo/file'
git -C './repo' merge -m "$((++number))" --no-overwrite-ignore branch2
git -C './repo' log --graph --all --patch
git -C './repo' status --verbose --verbose
cat './repo/file'

What did you expect to happen? (Expected behavior)

`git merge --no-overwrite-ignore` refuses to overwrite ignored files
when merge with conflict.
`git merge --no-overwrite-ignore` refuses to overwrite ignored files
when merge without conflict.

What happened instead? (Actual behavior)

`git merge --no-overwrite-ignore` overwrites ignored files when merge
with conflict.
`git merge --no-overwrite-ignore` overwrites ignored files when merge
without conflict.

What's different between what you expected and what actually happened?

Anything else you want to add:

(`git merge --no-overwrite-ignore` refuses to overwrite ignored files
when fast-forward.)
cd '/'; cd '/'; rm --force --recursive -- './test_git'; mkdir "$_"; cd "$_";
mkdir --parents -- './repo';
git init './repo'
branch_default_path="$(git -C './repo' symbolic-ref HEAD)"
branch_default_name="${branch_default_path#'refs/heads/'}"
echo 'file' >'./repo/.gitignore'; git -C './repo' add './.gitignore';
git -C './repo' commit -m "$((++number))"
git -C './repo' branch branch1
rm './repo/.gitignore'; git -C './repo' add './.gitignore'; echo '1'
>'./repo/file'; git -C './repo' add './file'; git -C './repo' commit
-m "$((++number))"
git -C './repo' checkout branch1
echo '2' >'./repo/file';
git -C './repo' log --graph --all --patch
git -C './repo' status --verbose --verbose
cat './repo/file'
git -C './repo' merge -m "$((++number))" --no-overwrite-ignore
"$branch_default_name"
git -C './repo' log --graph --all --patch
git -C './repo' status --verbose --verbose
cat './repo/file'

Please review the rest of the bug report below.
You can delete any lines you don't wish to share.


[System Info]
git version:
git version 2.46.0.windows.1
cpu: x86_64
built from commit: 2e6a859ffc0471f60f79c1256f766042b0d5d17d
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
feature: fsmonitor--daemon
libcurl: 8.9.0
OpenSSL: OpenSSL 3.2.2 4 Jun 2024
zlib: 1.3.1
uname: Windows 10.0 22631
compiler info: gnuc: 14.1
libc info: no libc information available
$SHELL (typically, interactive shell): C:\Program Files\Git\usr\bin\bash.exe


[Enabled Hooks]
not run from a git repository - no hooks to show

             reply	other threads:[~2024-09-01 10:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-01 10:49 Han Jiang [this message]
2024-09-03 23:19 ` `git merge --no-overwrite-ignore` overwrites ignored files when merge (i.e. not fast-forward) Elijah Newren
2024-09-04 11:03   ` Han Jiang

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='CANrWfmRvtz=WOPpv54-22aEFsCPi_vwpFo_Q08vq31NjggOVsw@mail.gmail.com' \
    --to=jhcarl0814@gmail.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).