{"thread":{"id":"7334","subject":"qiuestion about Git and Cogito","startedAt":"2007-03-20T15:15:32Z","lastAt":"2007-03-22T17:57:22Z","messageCount":3,"participants":["Francois Lang","Petr Baudis"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"37624","messageId":"45FFFA94.4040105@mail.nih.gov","threadId":"7334","inReplyTo":null,"subject":"qiuestion about Git and Cogito","fromName":"Francois Lang","fromEmail":"flang@mail.nih.gov","sentAt":"2007-03-20T15:15:32Z","receivedAt":"2007-03-20T15:15:32Z","isPatch":false,"sender":{"key":"flang@mail.nih.gov","avatar":null},"body":"Hello. We have started using Git and Cogito, and are very happy users so \nfar. There's one thing that I haven't been able to figure out, however:\n\nSuppose I've done a bunch of commits in my local repository that I have \nnot yet pushed to the remote repository. How can I determine what has \nbeen cg-commit-ed but not yet cg-pushe-ed WITHOUT actually doing the \ncg-push?\n\nMany thanks in advance for your help.\n\nFrancois Lang\nSenior Scientific Systems Programmer\nNational Library of Medicine\n"},{"id":"37630","messageId":"20070320155623.GH4489@pasky.or.cz","threadId":"7334","inReplyTo":"45FFFA94.4040105@mail.nih.gov","subject":"Re: qiuestion about Git and Cogito","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2007-03-20T15:56:23Z","receivedAt":"2007-03-20T15:56:23Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"On Tue, Mar 20, 2007 at 04:15:32PM CET, Francois Lang wrote:\n> Hello. We have started using Git and Cogito, and are very happy users so \n> far. There's one thing that I haven't been able to figure out, however:\n> \n> Suppose I've done a bunch of commits in my local repository that I have \n> not yet pushed to the remote repository. How can I determine what has \n> been cg-commit-ed but not yet cg-pushe-ed WITHOUT actually doing the \n> cg-push?\n> \n> Many thanks in advance for your help.\n\nAssuming that you work on master and push to origin,\n\n\tcg-log -r master..origin\n\nor\n\n\tcg-diff -r master..origin\n\nrespectively.\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nEver try. Ever fail. No matter. // Try again. Fail again. Fail better.\n\t\t-- Samuel Beckett\n"},{"id":"37753","messageId":"20070322175722.GP18276@pasky.or.cz","threadId":"7334","inReplyTo":"46028B45.2010802@mail.nih.gov","subject":"Re: qiuestion about Git and Cogito","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2007-03-22T17:57:22Z","receivedAt":"2007-03-22T17:57:22Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"On Thu, Mar 22, 2007 at 02:57:25PM CET, Francois Lang wrote:\n> Interesting...for me, when I do what you suggested, i.e.,\n> \n> cg-log -r master..origin\n> \n> it does not tell me what has been locally committed but not yet pushed.\n> \n> To get that behavior, I need to do\n> \n> cg-log -r origin..master.\n> \n> Does that make sense to you, or am I confused? I do work on master and \n> push to origin.\n\nOh, of course - I got it swapped in my head. :-)\n\nIt isn't the most intuitive syntax, admittedly, but I couldn't think of\nanything better. The way to think about it is \"show me the commits\nthat appeared between origin and master\", where\n\n\ta - b - c - d - e\n\t origin ^\n\t         master ^\n\nthus it will show the locally committed but not yet pushed d and e. This\nmaps nicely to the range syntax if you think about it, but it isn't\nterribly intuitive. :-(\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nEver try. Ever fail. No matter. // Try again. Fail again. Fail better.\n\t\t-- Samuel Beckett\n"}]}