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

Improve `git log -L` functionality

From
KKES <kes-kes@yandex.ru>
Date
Mar 6, 2018, 15:46 UTC
Message-ID
<2051651520351198@web40j.yandex.ru>
Hi.
 I want to `Trace the evolution of the line range`. 
And not committed change is sort of evolution and should be taken into account by -L option. 

Currently I MUST `stash save` change, look actual line number, trace evolution, `stash pop` to bring back current change.

EXPECTED: Allow to use those line numbers which I see in my editor without excess `stash save/stash pop` commands

If file has not committed change then this change maybe shown by `-L` as commit NOT COMMITTED YET If file staged 'commit STAGED'

More description what is comming on: https://stackoverflow.com/q/49130112/4632019

Next: KES
Message 1 of 3 in “Improve `git log -L` functionality”
  1. KESMar 6, 2018
  2. KESMar 10, 2018
  3. Ævar Arnfjörð BjarmasonMar 10, 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.