From: Vladimir Gorshenin <gorshenin.vladimir@googlemail.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Git@vger.kernel.org
Subject: Re: Git archeology
Date: Tue, 24 Apr 2018 12:31:47 +0200 [thread overview]
Message-ID: <CAEbJ=SOkfHHrmbUXP_niRP4S0HSENqXriGWNFoYX2XpdvWzZww@mail.gmail.com> (raw)
In-Reply-To: <20180421062923.4467-1-szeder.dev@gmail.com>
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 file despite only few lines were actually altered.
I would like to have an output form 'git log -L' in patch style. Could
it be done somehow?
Have a nice day,
Vladimir
2018-04-21 8:29 GMT+02:00 SZEDER Gábor <szeder.dev@gmail.com>:
>> 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'.
>
next prev parent reply other threads:[~2018-04-24 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-21 6:19 Git archeology Vladimir Gorshenin
2018-04-21 6:29 ` SZEDER Gábor
2018-04-24 10:31 ` Vladimir Gorshenin [this message]
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=SOkfHHrmbUXP_niRP4S0HSENqXriGWNFoYX2XpdvWzZww@mail.gmail.com' \
--to=gorshenin.vladimir@googlemail.com \
--cc=Git@vger.kernel.org \
--cc=szeder.dev@gmail.com \
/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.