Re: File rename impacts Gitlab history

[Guy Harris <gharris () sonic net>]

On Feb 26, 2021, at 8:48 AM, chuck c <bubbasnmp () gmail com> wrote:

> https://gitlab.com/wireshark/wireshark/-/commit/50dbe4df7fd7a5e4e1a27fd5046981486d350994
> Rename packet-ssl* to packet-tls*
>
> Looking through history of 
> https://gitlab.com/wireshark/wireshark/-/commits/master/epan/dissectors/packet-tls.c
>
> https://gitlab.com/wireshark/wireshark/-/tree/2fd42045f5afb556a03d8a1090f3278c77798766
>  "epan/dissectors/packet-tls.c" did not exist on "2fd42045f5afb556a03d8a1090f3278c77798766"
>
> Is there any sort of work around (symbolic link?) that could be tracked in Git?

If you can use Full Frontal Command-Line Git, --follow is a helpful command line for some Git commands:

$ git log epan/dissectors/packet-tls.c | egrep 2fd42045f5afb556a03d8a1090f3278c77798766
$ git log --follow epan/dissectors/packet-tls.c | egrep 2fd42045f5afb556a03d8a1090f3278c77798766
commit 2fd42045f5afb556a03d8a1090f3278c77798766

but it doesn't necessarily work for all commands, and I don't know whether there's any special trick for GitLab's Web 
interface.
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe