From: Phillip Wood <phillip.wood123@gmail.com>
To: Andreas Wiesinger <awiesing90@gmail.com>, git@vger.kernel.org
Subject: Re: [BUG]: Destructive behaviour of git revert
Date: Tue, 30 Jul 2019 19:36:17 +0100 [thread overview]
Message-ID: <015916f3-9386-d541-0603-b361c44a7ae8@gmail.com> (raw)
In-Reply-To: <CAP82knOVE5RbcDbD-SqbkoZ_4qubi96n2p3M_vgc4xGFVwTpMw@mail.gmail.com>
Hi Andreas
On 30/07/2019 18:24, Andreas Wiesinger wrote:
> Hello,
>
> git revert for merges will mark merged files as deleted and commit
> them as if they would have been deleted, but that is for sure never
> what anybody would expect and has deleted many files unintentionally
> and unrecognized in our repo shortly.
>
> I have reproduced this issue in a very small example repo here:
> https://gitlab.com/electrocnic/git-revert-destructive-behaviour/tree/master
>
> Expected behaviour would be:
>
> A reverted merge should never mark any files or directories as
> "deleted", and merging the branch where the other merge has been
> reverted should not lead to the deletion of those files.
Thanks for creating an example. I've had a quick look at it and it
appears that you have a merge that adds a new file from the branch being
merged, then when you revert the merge that file is deleted. Could you
explain what you want to happen when you revert that merge? The idea of
revert is to undo the changes introduced by the commit that is being
reverted, I'm struggling to understand why you think revert should not
do this for files that are added.
Best Wishes
Phillip
> I classify this behaviour as really really destructive and clearly a
> bug, even if this behaviour is by intention. It should not be by
> intention then..
>
> Best regards,
> Andreas
>
prev parent reply other threads:[~2019-07-30 18:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP82knNJ7YH30R-Z61ake58qERp--6hdvgGasKpHQ2TbMPraiA@mail.gmail.com>
2019-07-30 17:24 ` [BUG]: Destructive behaviour of git revert Andreas Wiesinger
2019-07-30 18:36 ` Phillip Wood [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=015916f3-9386-d541-0603-b361c44a7ae8@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=awiesing90@gmail.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).