Try to figure out which flags you should to pass to git log to dump all the info you needĦ. Realize that's not quite enough to narrow down your search to a single commit (maybe you want to see the diffs or file paths or something else?)ĥ. Look through the commit messages/dates/namesĤ. Dump the entire log output into a temporary fileģ. I know I use Browse Repository as well as the GUI logs pretty frequently, and they're godsends compared to your solution.Īnd lastly: this is what your solution actually looks like:ġ. I mean, nobody said this 1 reason should be enough to make you switch tools? I was just giving an example.Īnd no, it's not "unusual" just because you say so to try to dismiss the problem. no need to change the tools just for this unusual action. > or git log > file and look at it in an editor. This misses the point of the problem - the point is you don't know precisely what string to grep for. git log | grep - find the hash of the one I want.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |