From: "Pascal Obry" <pascal@obry.net>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: rebase, file permissions and removed file
Date: Mon, 27 Oct 2008 15:02:42 +0100 [thread overview]
Message-ID: <a2633edd0810270702x416bb659ke183b0cc6266071@mail.gmail.com> (raw)
In short,
- a branch is created
- a file is removed from master
- the same file has its permissions changed on the branch
- we rebase the branch on master
- how to resolve the conflict?
Following is a script to reproduce the problem, see comment at the end.
Any idea? Thanks.
<<
-- #!/bin/sh
rm -fr repo
mkdir repo
cd repo
git init
touch file1 file2
chmod a+x file*
git add .
git ci -m "First rev"
git checkout -b fixperms
chmod a-x file1
git add file1
git ci -m "Fix perm file1"
git checkout master
git rm file1
git ci -m "Remove file1"
git checkout fixperms
git rebase master
# At this point there is a conflict as expected
# file1 has been removed on master, and file1 had its permissions changed
# on fixperms branch.
#
# What I find confusing is that:
# $ git diff
# and
# $ git diff --cached
#
# are reporting nothing.
#
# Ok, file1 has been removed, let's then remove it as it is right:
#
# $ git rm file1
# fatal: pathspec 'file1' did not match any files
#
# Ok, so what's the proper way to fix that! What should I do to be able to
# continue the rebase:
#
# $ git rebase --continue
>>
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595
next reply other threads:[~2008-10-27 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 14:02 Pascal Obry [this message]
2008-10-27 14:38 ` rebase, file permissions and removed file Johannes Sixt
2008-10-27 15:09 ` Pascal Obry
2008-10-27 15:21 ` Johannes Sixt
2008-10-27 15:33 ` Pascal Obry
2008-10-27 16:39 ` Samuel Tardieu
2008-10-27 17:12 ` Pascal Obry
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=a2633edd0810270702x416bb659ke183b0cc6266071@mail.gmail.com \
--to=pascal@obry.net \
--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).