Following Git(Hub) History

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Following Git(Hub) History

Sean P. DeNigris
Administrator
Does anyone have any strategies for following git histories past code
reorganizations (see steps #2 and #5 below)?

My typical experience is:
1. Do blame or history on a file
2. Follow it back to the inevitable "convert to tonel"
3. Go to that commit's parent
4. View repo files at that point
5. Follow back to "rename code subfolder"
6. Repeat steps 3 - 5 as necessary until I find the version I need or
"initial commit porting from StHub!"



-----
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Cheers,
Sean
Reply | Threaded
Open this post in threaded view
|

Re: Following Git(Hub) History

Guillermo Polito


> El 6 ago 2019, a las 0:48, Sean P. DeNigris <[hidden email]> escribió:
>
> Does anyone have any strategies for following git histories past code
> reorganizations (see steps #2 and #5 below)?
>
> My typical experience is:
> 1. Do blame or history on a file
> 2. Follow it back to the inevitable "convert to tonel"
> 3. Go to that commit's parent
> 4. View repo files at that point
> 5. Follow back to "rename code subfolder"
> 6. Repeat steps 3 - 5 as necessary until I find the version I need or
> "initial commit porting from StHub!”

Have you tried a

$git log —follow

?

The follow option will take into account file renames and moves, simplifying at least steps 3-6.

>
>
>
> -----
> Cheers,
> Sean
> --
> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html
>


Reply | Threaded
Open this post in threaded view
|

Re: Following Git(Hub) History

Sean P. DeNigris
Administrator
Guillermo Polito wrote
> $git log —follow

Didn't know about that one. Thanks! I'll try and report back...



-----
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Cheers,
Sean