On Mon, Jan 25, 2010 at 12:37:14 +0100, Juliusz Chroboczek wrote: > > You can create a branch 'for-chris' with 'git checkout -b for-chris'. > > Then run 'git rebase -i origin/master' and delete the lines > > corresponding to commits you don't want to include. > > That's exactly what I'm doing above. But you're omitting some minor > details: > You had more rebase steps that didn't seem necessary.
> - git push is dumb, I need to set up the remote first; You don't have to, you can give it the repo's url if you're too lazy to add a remote. But then again, adding the remote is something you only have to do once. > - git push is dense, I need to rebase the for-chris branch first; I'm not sure what you mean here. You had an earlier for-chris branch on the remote repo that doesn't fast-forward to the new one? Rebasing the remote branch, or forcing the push, is probably not a good idea. It's better to use a different name, or base the new pull request on the old for-chris branch? > - git push is dim, I need to manually ensure I'm not discarding > anything when I push. > Not if the push is fast-forward and you don't force it. Cheers, Julien ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Polipo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/polipo-users
