{"thread":{"id":"47990","subject":"Improve `git log -L` functionality","startedAt":"2018-03-06T15:54:40Z","lastAt":"2018-03-10T12:28:39Z","messageCount":3,"participants":["KES","Ævar Arnfjörð Bjarmason"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"341132","messageId":"2051651520351198@web40j.yandex.ru","threadId":"47990","inReplyTo":null,"subject":"Improve `git log -L` functionality","fromName":"KES","fromEmail":"kes-kes@yandex.ru","sentAt":"2018-03-06T15:46:38Z","receivedAt":"2018-03-06T15:54:40Z","isPatch":false,"sender":{"key":"kes-kes@yandex.ru","avatar":null},"body":"Hi.\n I want to `Trace the evolution of the line range`. \nAnd not committed change is sort of evolution and should be taken into account by -L option. \n\nCurrently I MUST `stash save` change, \nlook actual line number, \ntrace evolution, \n`stash pop` to bring back current change. \n\nEXPECTED:\nAllow to use those line numbers which I see in my editor\nwithout excess `stash save/stash pop` commands\n\nIf file has not committed change then this change maybe shown by `-L` as commit NOT COMMITTED YET\nIf file staged 'commit STAGED'\n\nMore description what is comming on:\nhttps://stackoverflow.com/q/49130112/4632019\n"},{"id":"341384","messageId":"3857311520679275@web8j.yandex.ru","threadId":"47990","inReplyTo":"2051651520351198@web40j.yandex.ru","subject":"Re: Improve `git log -L` functionality","fromName":"KES","fromEmail":"kes-kes@yandex.ru","sentAt":"2018-03-10T10:54:35Z","receivedAt":"2018-03-10T10:54:42Z","isPatch":false,"sender":{"key":"kes-kes@yandex.ru","avatar":null},"body":"uh... seems nobody is interested in this functionality (\n\n06.03.2018, 17:46, \"KES\" <kes-kes@yandex.ru>:\n> Hi.\n>  I want to `Trace the evolution of the line range`.\n> And not committed change is sort of evolution and should be taken into account by -L option.\n>\n> Currently I MUST `stash save` change,\n> look actual line number,\n> trace evolution,\n> `stash pop` to bring back current change.\n>\n> EXPECTED:\n> Allow to use those line numbers which I see in my editor\n> without excess `stash save/stash pop` commands\n>\n> If file has not committed change then this change maybe shown by `-L` as commit NOT COMMITTED YET\n> If file staged 'commit STAGED'\n>\n> More description what is comming on:\n> https://stackoverflow.com/q/49130112/4632019\n"},{"id":"341391","messageId":"87fu58qfm9.fsf@evledraar.gmail.com","threadId":"47990","inReplyTo":"3857311520679275@web8j.yandex.ru","subject":"Re: Improve `git log -L` functionality","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2018-03-10T12:28:30Z","receivedAt":"2018-03-10T12:28:39Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"\nOn Sat, Mar 10 2018, KES jotted:\n\n> uh... seems nobody is interested in this functionality (\n\nI'm interested in this, and would review a patch to implement this.\n\nGenerally speaking when you send a \"wouldn't it be neat if...\" message\nto the Git mailing list a lot of people read it (including myself at the\ntime), but don't find it useful to add anything to it.\n\nSure, this feature as described would be neat if it existed, but without\na patch there's not much to discuss.\n\nIn particular the trade-offs of teaching the log machinery to somehow\nstitch together the worktree state without the user somehow getting the\nstate into a tree may not be worth it, or it may be. We'd have to have a\nworking patch to see.\n\nSo if you're interested in working on this don't let the seeming lack of\ninterest discourage you.\n\n> 06.03.2018, 17:46, \"KES\" <kes-kes@yandex.ru>:\n>> Hi.\n>> I want to `Trace the evolution of the line range`.\n>> And not committed change is sort of evolution and should be taken into account by -L option.\n>>\n>> Currently I MUST `stash save` change,\n>> look actual line number,\n>> trace evolution,\n>> `stash pop` to bring back current change.\n>>\n>> EXPECTED:\n>> Allow to use those line numbers which I see in my editor\n>> without excess `stash save/stash pop` commands\n>>\n>> If file has not committed change then this change maybe shown by `-L` as commit NOT COMMITTED YET\n>> If file staged 'commit STAGED'\n>>\n>> More description what is comming on:\n>> https://stackoverflow.com/q/49130112/4632019\n"}]}