![]() In fact sometimes a co-developer at the other end of the world says, look at this, could it be useful to you (knowing what I am working at)?Īt the end, if it's useful for one file, it's also useful for a whole commit. Well, it's often used in teams that are very cooperative. all lead to conflict situations.ĭirectly comparing with and editing the working tree is a lean operation like a shortcut. Most operations don't like local changes. It's simply more convenient to do it live than to start committing my changes, then do a compare and then split or something to get it together. Now I want to see, if I have to bother with conflicts with these changes or if I can borrow something to ease the merge.Īll before the more expensive operations. I have changes and some incoming branch has also changes in the same area. I could stash my changes, but I may have done a similar change. But I may already have staged something while the rest should be kept unstaged. It's only possible by first staging my own changes. It's easily done for a single file, just do "Compare with Working Tree" (as Thomas keeps mentioning).īut if the changes are distributed over several files, I am not even able to find these. Now I want to import only a certain part of it (lets say I'm working on other spelling errors or translation). This may be lazyness, or working on several things at once, or correcting spelling or translation errors while working on something. Someone has committed something which should really be two or even more commits. The object I see is the one to operate on. TortoiseGit is an easy to use client for the Git distributed revision. ![]() Like Leonardo said it's the logical thing to do.Ī Working Tree is a working tree and not the index. Popular Alternatives to SmartGit for Windows, Mac, Linux, Web, iPad and more. In fact I just learned that it's only compared to the index.which explains why I am wondering from time to time why I didn't see that particular difference, now I know. ![]()
0 Comments
Leave a Reply. |