Re: commit gone after merge - how to debug?
- From
- Igor Lautar <igor.lautar@gmail.com>
- Date
- Nov 26, 2012, 13:24 UTC
- Message-ID
- <CAO1Khk_r5eubm6M815FCxXLRpm-zPhzfFasug497saev8o-qeQ@mail.gmail.com>
- In-Reply-To
- <1353935441-ner-9639@calvin>
On Mon, Nov 26, 2012 at 2:10 PM, Tomas Carnecky <tomas.carnecky@gmail.com> wrote:
Show 5 quoted lines
> On Mon, 26 Nov 2012 14:06:09 +0100, Igor Lautar <igor.lautar@gmail.com> wrote: >> git log <file modified by commit> >> - commit NOT shown in file history any more and file does not have this change > > does `git log --full-history <file modified by commit>` show the commit?
Indeed it does.
Did the merge with verbosity set to 5. It says the commit I'm merging in is virtual (probably as it is a merge commit in itself?).
Why would commit be left behind after merge? What kind of history triggers this scenario? Just trying to understand reasoning as its counter-intuitive to what I know now. This may affect our workflow (ie., change it so we avoid it happening).