From: Ramkumar Ramachandra <artagnon@gmail.com>
To: git@vger.kernel.org
Subject: Branch merge bug
Date: Tue, 19 Jan 2010 12:52:58 +0530 [thread overview]
Message-ID: <f3271551001182322p86a02d8p8b9ceb49e930d333@mail.gmail.com> (raw)
A friend showed me this reduced test case. It seems to work fine with
bzr and hg. Is this a git bug?
>: git --version
git version 1.6.3.1
>: git init
Initialized empty Git repository in /Users/lut4rp/Code/tester/.git/
>: echo asdjhaskd >fil
>: git add fil
>: git cm 'initial commit'
[master (root-commit) 9983161] initial commit
1 files changed, 1 insertions(+), 0 deletions(-)
create mode 100644 fil
>: git branch new
>: git branch
* master
new
>: git mv fil fila
>: git status
# On branch master
# Changes to be committed:
# (use "git reset HEAD <file>..." to unstage)
#
# renamed: fil -> fila
#
>: git cm 'renamed to fila'
[master 9de0953] renamed to fila
1 files changed, 0 insertions(+), 0 deletions(-)
rename fil => fila (100%)
>: git co new
Switched to branch 'new'
>: git rm fil
rm 'fil'
>: echo asjhdajkhsdkajhs >fila
>: git add fila
>: git cm 'renamed, heavily modified'
[new 5914271] renamed, heavily modified
2 files changed, 2 insertions(+), 1 deletions(-)
delete mode 100644 fil
create mode 100644 fila
>: git co master
Switched to branch 'master'
>: git merge new
CONFLICT (rename/delete): Rename fil->fila in HEAD and deleted in new
Automatic merge failed; fix conflicts and then commit the result.
>: cat fila
asdjhaskd #### Still the master
branch's content, `merge` apparently did nothing.
>: git show :2:fila
asdjhaskd
>: git show :3:fila
fatal: ambiguous argument ':3:fila': unknown revision or path not in
the working tree.
Use '--' to separate paths from revisions
>: git show new:fila
asjhdajkhsdkajhs
ajksh askjdhaksdh kajshdk asd
next reply other threads:[~2010-01-19 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 7:22 Ramkumar Ramachandra [this message]
2010-01-19 12:07 ` Branch merge bug Michael J Gruber
2010-01-19 12:39 ` Andreas Krey
2010-01-19 13:22 ` Ramkumar Ramachandra
2010-01-19 13:58 ` Michael J Gruber
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=f3271551001182322p86a02d8p8b9ceb49e930d333@mail.gmail.com \
--to=artagnon@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).