Miklos Vajna writes:
> Hi,
>
> I was trying to understand the history of a piece of code in LibreOffice
> and I'm facing a behaviour of git-log which is not something I can
> explain. I'm not sure if this is a git bug or a user error. ;)
>
> Here is the situation:
>
> git clone git://anongit.free
Hi Jonathan,
On Tue, Feb 04, 2014 at 11:48:42AM -0800, Jonathan Nieder
wrote:
> Luckily '-m -p' without --first-parent worked and the first commit it
> showed was the right one. It produces more hits than I'd like, too,
> though.
Ah, excellent! :-) '-m' does what I need.
Thanks a lot,
Miklos
Hi,
Miklos Vajna wrote:
> git clone git://anongit.freedesktop.org/libreoffice/core
> cd core
> git log --full-history -p -S'mnTitleBarHeight ='
> sd/source/ui/dlg/PaneDockingWindow.cxx
>
> Here the first output I get from git-log is
> b390fae1706b9c511158a03e4fd61f263be4e511, where you can see t
On Tue, Feb 04, 2014 at 06:37:13PM +0100, Miklos Vajna
wrote:
> But then I run:
>
> git grep 'mnTitleBarHeight =' sd
>
> and it's not there. Am I missing something, as in e.g. even with
> --full-history git-log does some simplification?
I tried to reproduce this with a repo from scratch, and i
Hi,
I was trying to understand the history of a piece of code in LibreOffice
and I'm facing a behaviour of git-log which is not something I can
explain. I'm not sure if this is a git bug or a user error. ;)
Here is the situation:
git clone git://anongit.freedesktop.org/libreoffice/core
cd core
g
5 matches
Mail list logo