Re: Git archeology

Hi Christian, Thank you for the reply. After I got the reply from Szedar I was so excited about git community passion for help. And your reply made me ever more assure in it. Once again thank your for the comprehensive answer. I appreciate Daniel German's research and going to try token based met

Re: Git archeology

Hi Szedar, Thank you for the reply! I didn't expect it could be so instant! I checked 'git log -L' option and it seems to the best one so far. But nevertheless is has a pit fall: I run it like 'git log -L ,:somefile' and get the output that needs manual scraping since each commit spans the whole

Re: Git archeology

Hi, On Sat, Apr 21, 2018 at 8:19 AM, Vladimir Gorshenin wrote: > Hi, > > My team and I as well as millions of other developers are excited to > have such tool at hand as Git. It helps us a lot. > > Now we challenged ourselves to be even more productive with Git > analyzing our usage history. Wha

Re: Git archeology

> And there is a problem, which I believe is fundamental for Git (please > prove me wrong): how to find all overlapping commits, e.g. touching > the same lines of code? You might be looking for 'git log -L'.

Git archeology

Hi, My team and I as well as millions of other developers are excited to have such tool at hand as Git. It helps us a lot. Now we challenged ourselves to be even more productive with Git analyzing our usage history. And there is a problem, which I believe is fundamental for Git (please prove me