On Mon, 25 May 2009, Tor Arntsen wrote: > So presumably you have your own cloned repo which you work in (just as the > rest of us), where you commit, and then push?
Exactly. > In that case, there's a nice trick - if you after a commit find that a > comment should be fixed or there's some other problem, then just git add the > changed file(s) and use git commit --amend, which will update the last > commit instead of making a new one. For example, commit ids 5a162.., > 42e9f0.., 160e5a.. looks like they could be a single one. Ah that's a nice one. Thanks. I'm really a rookie in the git world so I'm grateful to get some pointers to good ideas/usages. > That won't do if you have pushed in the meantime of course In this case I believe I had pushed the commits already, but I'll keep this trick in mind for the future! -- / daniel.haxx.se ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://www.creativitycat.com _______________________________________________ libssh2-devel mailing list libssh2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libssh2-devel
