Menu
▾
▴
Re: Unreleased fixes in master
|
From: Ethan A M. <sf...@us...> - 2019-02-22 22:39:26
|
On Friday, February 22, 2019 1:57:37 PM PST Ethan A Merritt via gnuplot-beta wrote:
> Exactly.
> This seems like a hint either that "git log" is the wrong tool
> or that it could be improved by tracking a bit more history.
> Can't the cherry-pick operation itself be recorded as a transaction?
> Then a hypothetical command option "git log --show-origin"
> would list entries as
>
> %%%
> [4] git status
> On branch branch-5-2-stable
>
> [5] git log --show-origin HEAD~1..HEAD
>
> commit d83adc16f5a572f5d004963ead8326591498dd41
> Author: Ethan A Merritt <merritt@u.washington.edu>
> Date: Tue Feb 19 23:10:08 2019 -0800
> Origin: cherry-pick from master/83a349a07b3f30d3f0c11ff80152f3cb96ff3c77
>
> <body of commit message text>
> %%%
After some delving I have discovered that this used to be the default in git
but for some reason it was removed!
The current documentation suggests that "git cherry-pick -x" may save the
history I want. So I will use that going forward.
thanks for putting up with my incomplete progress as a git user
Ethan
|
