git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Saksham Mittal <saksham.mittal000@gmail.com>
To: schiff.michael@gmail.com
Cc: git@vger.kernel.org
Subject: Re: Possible merge bug
Date: Thu, 11 Nov 2021 16:50:44 +0530	[thread overview]
Message-ID: <5aa1fb67-6bd8-6de3-8271-369722b6ebef@gmail.com> (raw)
In-Reply-To: <CAJcz5TVsv20+FmHR67_UhL_7rhEGvfPHeP3RMiRtnSGAEKiwBg@mail.gmail.com>

Hello there,

I wrote a small script as well that automates testing this use case as well, but I don't really know what the policy is on attachments in git, seeing as how it's my first time contributing to git.

I am on git version 2.33.1 on Fedora 35, but I am not seeing the bug while running the script. So, I grabbed the git source code and built it. This version is 2.34.0.rc2.9.g4d53e91c6b, not quite your version but I tried to go back to the commit you mentioned and build it, but I faced some errors and no binary would build.

Anyway, the version I built and tested also did not permit auto merge and required me to manually make changes as well, so the issue seems to have been fixed.

You can take a look at my script as well, I followed your instructions as best I could and built this:

#!/bin/bash

git --version

mkdir sample
cd sample
git init
echo -e "a\nb\nc\n" > test
git add .
git commit -m "abc"

git branch b1
git switch b1

echo -e "b\na\nc" > test
git add .
git commit -m "bac"

git switch main
git branch b2
git switch b2

echo -e "b\nc\na" > test
git add .
git commit -m "bca"

git switch main
git merge b1
git merge b2

git log --graph --oneline --all


Cheers,

Saksham Mittal




  reply	other threads:[~2021-11-11 11:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02  6:26 Possible merge bug Michael Schiff
2021-11-11 11:20 ` Saksham Mittal [this message]
2021-11-11 14:28   ` Philippe Blain
2021-11-13  3:49     ` Michael Schiff
2021-11-13  7:11       ` Johannes Sixt

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=5aa1fb67-6bd8-6de3-8271-369722b6ebef@gmail.com \
    --to=saksham.mittal000@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=schiff.michael@gmail.com \
    /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).