git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git archeology

From
VGVladimir Gorshenin <gorshenin.vladimir@googlemail.com>
Date
Apr 24, 2018, 10:31 UTC
Message-ID
<CAEbJ=SOkfHHrmbUXP_niRP4S0HSENqXriGWNFoYX2XpdvWzZww@mail.gmail.com>
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>:
Show 6 quoted lines
>> 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'.
>
Previous: SZEDER GáborNext: Christian Couder
Message 3 of 5 in “Git archeology”
  1. Vladimir GorsheninApr 21, 2018
  2. SZEDER GáborApr 21, 2018
  3. Vladimir GorsheninApr 24, 2018
  4. Christian CouderApr 21, 2018
  5. Vladimir GorsheninApr 24, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.