All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Gorshenin <gorshenin.vladimir@googlemail.com>
To: Git@vger.kernel.org
Subject: Git archeology
Date: Sat, 21 Apr 2018 08:19:12 +0200	[thread overview]
Message-ID: <CAEbJ=SN0h_eO+0CJQGEnEafhzgAYdgXByUqb_vsC1rgGw7jNAw@mail.gmail.com> (raw)

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 wrong): how to find all overlapping commits, e.g. touching
the same lines of code?

I played with “Git diff” and “Git blame” but without a reliable
result. “Git diff” gives only relative number of lines and it’s not
easy to track these number through 1000+ commits. “Git blame” has nice
output but without any information about deletion.

What would you advice me to do?

Regards,
Wladd

             reply	other threads:[~2018-04-21  6:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-21  6:19 Vladimir Gorshenin [this message]
2018-04-21  6:29 ` Git archeology SZEDER Gábor
2018-04-24 10:31   ` Vladimir Gorshenin
2018-04-21  6:43 ` Christian Couder
2018-04-24 10:37   ` Vladimir Gorshenin

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAEbJ=SN0h_eO+0CJQGEnEafhzgAYdgXByUqb_vsC1rgGw7jNAw@mail.gmail.com' \
    --to=gorshenin.vladimir@googlemail.com \
    --cc=Git@vger.kernel.org \
    /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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.