On Mon, Nov 26, 2012 at 2:10 PM, Tomas Carnecky <[email protected]> wrote: > On Mon, 26 Nov 2012 14:06:09 +0100, Igor Lautar <[email protected]> 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). -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
