On Mon, May 25, 2009 at 11:50, Daniel Stenberg <dan...@haxx.se> wrote: > On Mon, 25 May 2009, Tor Arntsen wrote: > >>> So you checkout from here => git://git.stuge.se/libssh2.git >> >> Hi, for my own curiosity (mostly - because it'll have an impact on the >> 'allow push' discussion too), is this repo a 'bare' (or 'naked') repo? Or is >> it the one you're working directly in? Or something different? > > That's the repo I'm pushing my work into and that the daily snapshots are > built from.
Ok, so then I assume it's a bare repo (i.e. just a libssh2.git/ directory). So presumably you have your own cloned repo which you work in (just as the rest of us), where you commit, and then push? 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. That won't do if you have pushed in the meantime of course, or if someone else has cloned your working repo. But it's quite useful otherwise. For my own stuff I clone repos between machines (typically different architectures) and fiddle with the changes that way before I finally pull changes back to my other cloned copies. -Tor ------------------------------------------------------------------------------ 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
