![]() No need to mess with a single temporary file, fire up your editor manually, or risk losing anything.Īnyway, again: this was just 1 example meant to get the idea across, hopefully with the aid of your imagination to extrapolate to other scenarios. Not only is the number of steps smaller, each one is also significantly faster, and less risky too. If it's not the file you want, press Escape and click again. Double-click each file you want to examine to see the diffĤ. ![]() Click on a commit with the date you're interested inģ. ![]() With a GUI log TortoiseGit's log, you literally:ġ. Remove the temporary file in your editor.Īnd somehow you always do all the above without making a mistake, otherwise have fun reverting or recovering lost data. Remove the temporary file you checked out.ġ4. Once you have a copy of that file, look through it, maybe examine/pull out the code you wanted (or whatever)ġ3. Figure out how to run git checkout-index -a -f -prefix=/destination/path/ so that you check the file out into a different directory.ġ2. Make will now rebuild everything.), ORġ1b. Run git stash, and now suddenly messing up your staging area that you'd carefully staged changes in, and also messing up the file metadata (e.g. (Hopefully,) before you press Enter, realize you're about to trash your current copy of the file, which had some other changesġ1a. Type 'git checkout COMMIT - file/path' once you find somethingġ0. Scroll through your file containing diffs/names/whatever extra info you dumpedĩ. Open the temp file again in your editorĨ. Call git log again, hopefully now it dumps all the info you needħ. 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 |