{"thread":{"id":"19019","subject":"auto commit merge using the default merge message","startedAt":"2009-04-23T07:46:05Z","lastAt":"2009-04-24T17:55:11Z","messageCount":10,"participants":["Caleb Cushing","Alex Riesen","Michael J Gruber","Junio C Hamano","Brian Gernhardt","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"112054","messageId":"81bfc67a0904230046j48ed06b7s5693406332ee52dc@mail.gmail.com","threadId":"19019","inReplyTo":null,"subject":"auto commit merge using the default merge message","fromName":"Caleb Cushing","fromEmail":"xenoterracide@gmail.com","sentAt":"2009-04-23T07:46:05Z","receivedAt":"2009-04-23T07:46:05Z","isPatch":false,"sender":{"key":"xenoterracide@gmail.com","avatar":"https://gravatar.com/avatar/af3f0745dfa0ea9c4ee551d7d0a3cfe7ba8d229754c11678ab2ed23c3fa57065?d=mp&s=160"},"body":"so I do the same merge all the time... sorta, I'm not sure rerere\nwould actually work because the file is different each time... I just\nhave to delete it each time. and I want to automate the process.\ncheckout merge rm commmit, problem is commit brings and editor up, I\nwant to commit with the 'auto inserted merge message' that is\ngenerated, without seeing the editor, how do I do this?\n\n-- \nCaleb Cushing\n\nhttp://xenoterracide.blogspot.com\n"},{"id":"112055","messageId":"81b0412b0904230057k1653d039vfc3962e6affda584@mail.gmail.com","threadId":"19019","inReplyTo":"81bfc67a0904230046j48ed06b7s5693406332ee52dc@mail.gmail.com","subject":"Re: auto commit merge using the default merge message","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2009-04-23T07:57:18Z","receivedAt":"2009-04-23T07:57:18Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"2009/4/23 Caleb Cushing :\n> so I do the same merge all the time... sorta, I'm not sure rerere\n> would actually work because the file is different each time... I just\n> have to delete it each time. and I want to automate the process.\n> checkout merge rm commmit, problem is commit brings and editor up, I\n> want to commit with the 'auto inserted merge message' that is\n> generated, without seeing the editor, how do I do this?\n\nSee git commit -C ,\ngit commit -F and git commit -m \"message text\".\n"},{"id":"112056","messageId":"49F025E7.7090404@drmicha.warpmail.net","threadId":"19019","inReplyTo":"81b0412b0904230057k1653d039vfc3962e6affda584@mail.gmail.com","subject":"Re: auto commit merge using the default merge message","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2009-04-23T08:25:11Z","receivedAt":"2009-04-23T08:25:11Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Alex Riesen venit, vidit, dixit 23.04.2009 09:57:\n> 2009/4/23 Caleb Cushing :\n>> so I do the same merge all the time... sorta, I'm not sure rerere\n>> would actually work because the file is different each time... I just\n>> have to delete it each time. and I want to automate the process.\n>> checkout merge rm commmit, problem is commit brings and editor up, I\n>> want to commit with the 'auto inserted merge message' that is\n>> generated, without seeing the editor, how do I do this?\n> \n> See git commit -C ,\n> git commit -F and git commit -m \"message text\".\n\nI think he wants the auto generated message which may be different for\neach merge. Maybe something like\n\nGIT_EDITOR=/bin/true git commit\n\nwill do the trick.\n\nMichael\n"},{"id":"112058","messageId":"7vocunwz1n.fsf@gitster.siamese.dyndns.org","threadId":"19019","inReplyTo":"49F025E7.7090404@drmicha.warpmail.net","subject":"Re: auto commit merge using the default merge message","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2009-04-23T08:32:20Z","receivedAt":"2009-04-23T08:32:20Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Michael J Gruber writes:\n\n> I think he wants the auto generated message which may be different for\n> each merge. Maybe something like\n>\n> GIT_EDITOR=/bin/true git commit\n>\n> will do the trick.\n\nUse \"GIT_EDITOR=:\" instead. It also is *true* just like /bin/true, but\ngit knows a simple magic about this and avoids an extra fork+exec.\n\nA similar trick exists for GIT_PAGER=cat (not \"/bin/cat\"), by the way.\n"},{"id":"112060","messageId":"49F02FC0.1010007@drmicha.warpmail.net","threadId":"19019","inReplyTo":"7vocunwz1n.fsf@gitster.siamese.dyndns.org","subject":"Re: auto commit merge using the default merge message","fromName":"Michael J Gruber","fromEmail":"git@drmicha.warpmail.net","sentAt":"2009-04-23T09:07:12Z","receivedAt":"2009-04-23T09:07:12Z","isPatch":false,"sender":{"key":"git@grubix.eu","avatar":"https://avatars.githubusercontent.com/u/233215?v=4"},"body":"Junio C Hamano venit, vidit, dixit 23.04.2009 10:32:\n> Michael J Gruber writes:\n> \n>> I think he wants the auto generated message which may be different\n>> for each merge. Maybe something like\n>> \n>> GIT_EDITOR=/bin/true git commit\n>> \n>> will do the trick.\n> \n> Use \"GIT_EDITOR=:\" instead. It also is *true* just like /bin/true,\n> but git knows a simple magic about this and avoids an extra\n> fork+exec.\n\nGood to know!\n\n> A similar trick exists for GIT_PAGER=cat (not \"/bin/cat\"), by the\n> way.\n> \n\nSo, GIT_PAGER=cat differs from GIT_PAGER=/bin/cat even when `which\ncat`==/bin/cat?\n\nMichael\n"},{"id":"112094","messageId":"CA5A92BB-29E5-40C0-BA9A-ED076676D8BF@silverinsanity.com","threadId":"19019","inReplyTo":"49F02FC0.1010007@drmicha.warpmail.net","subject":"Re: auto commit merge using the default merge message","fromName":"Brian Gernhardt","fromEmail":"benji@silverinsanity.com","sentAt":"2009-04-23T16:19:03Z","receivedAt":"2009-04-23T16:19:03Z","isPatch":false,"sender":{"key":"benji@silverinsanity.com","avatar":"https://gravatar.com/avatar/e06c101dbc25c68114d859b4a9ec7cf8a2c52fd2b0270ef0eac0e2e63ff22311?d=mp&s=160"},"body":"\nOn Apr 23, 2009, at 5:07 AM, Michael J Gruber wrote:\n\n> Junio C Hamano venit, vidit, dixit 23.04.2009 10:32:\n>> Use \"GIT_EDITOR=:\" instead. It also is *true* just like /bin/true,\n>> but git knows a simple magic about this and avoids an extra\n>> fork+exec.\n>\n> Good to know!\n>\n>> A similar trick exists for GIT_PAGER=cat (not \"/bin/cat\"), by the\n>> way.\n>>\n>\n> So, GIT_PAGER=cat differs from GIT_PAGER=/bin/cat even when `which\n> cat`==/bin/cat?\n\nYes, if $GIT_PAGER == \"cat\", then git won't launch a pager at all. If \n$GIT_PAGER == \"/bin/cat\", then git will launch /bin/cat and pipe all \nof it's output through it. The result is (assuming a functional /bin/ \ncat) identical, but \"cat\" avoids the extra memory usage of \"/bin/cat\".\n\n~~ Brian\n"},{"id":"112149","messageId":"81bfc67a0904231831y31bfb057pa5eaa86d0e153824@mail.gmail.com","threadId":"19019","inReplyTo":"7vocunwz1n.fsf@gitster.siamese.dyndns.org","subject":"Re: auto commit merge using the default merge message","fromName":"Caleb Cushing","fromEmail":"xenoterracide@gmail.com","sentAt":"2009-04-24T01:31:10Z","receivedAt":"2009-04-24T01:31:10Z","isPatch":false,"sender":{"key":"xenoterracide@gmail.com","avatar":"https://gravatar.com/avatar/af3f0745dfa0ea9c4ee551d7d0a3cfe7ba8d229754c11678ab2ed23c3fa57065?d=mp&s=160"},"body":"On Thu, Apr 23, 2009 at 4:32 AM, Junio C Hamano wrote:\n> Use \"GIT_EDITOR=:\" instead.  It also is *true* just like /bin/true, but\n> git knows a simple magic about this and avoids an extra fork+exec.\n>\n\nSo I could put\n\nGIT_EDITOR=:\n\nat the top of my shell script, and then whenever I need to do a\ncommit, just git commit and it'll work (assuming the commit has a\ndefault message).\n\n-- \nCaleb Cushing\n\nhttp://xenoterracide.blogspot.com\n"},{"id":"112185","messageId":"20090424140606.GB10761@coredump.intra.peff.net","threadId":"19019","inReplyTo":"81bfc67a0904231831y31bfb057pa5eaa86d0e153824@mail.gmail.com","subject":"Re: auto commit merge using the default merge message","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-04-24T14:06:06Z","receivedAt":"2009-04-24T14:06:06Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Apr 23, 2009 at 09:31:10PM -0400, Caleb Cushing wrote:\n\n> On Thu, Apr 23, 2009 at 4:32 AM, Junio C Hamano wrote:\n> > Use \"GIT_EDITOR=:\" instead.  It also is *true* just like /bin/true, but\n> > git knows a simple magic about this and avoids an extra fork+exec.\n> >\n> \n> So I could put\n> \n> GIT_EDITOR=:\n> \n> at the top of my shell script, and then whenever I need to do a\n> commit, just git commit and it'll work (assuming the commit has a\n> default message).\n\nYou need to also\n\n export GIT_EDITOR\n\nfor \"git commit\" to see it.\n\n-Peff\n"},{"id":"112221","messageId":"81bfc67a0904241050t26a0ed62vbf17e471ddc10672@mail.gmail.com","threadId":"19019","inReplyTo":"20090424140606.GB10761@coredump.intra.peff.net","subject":"Re: auto commit merge using the default merge message","fromName":"Caleb Cushing","fromEmail":"xenoterracide@gmail.com","sentAt":"2009-04-24T17:50:57Z","receivedAt":"2009-04-24T17:50:57Z","isPatch":false,"sender":{"key":"xenoterracide@gmail.com","avatar":"https://gravatar.com/avatar/af3f0745dfa0ea9c4ee551d7d0a3cfe7ba8d229754c11678ab2ed23c3fa57065?d=mp&s=160"},"body":"On Fri, Apr 24, 2009 at 10:06 AM, Jeff King wrote:\n> export GIT_EDITOR\n>\n\nmaybe I'm being silly, but won't that then affect my interactive shells?\n\n-- \nCaleb Cushing\n\nhttp://xenoterracide.blogspot.com\n"},{"id":"112223","messageId":"20090424175511.GA11360@coredump.intra.peff.net","threadId":"19019","inReplyTo":"81bfc67a0904241050t26a0ed62vbf17e471ddc10672@mail.gmail.com","subject":"Re: auto commit merge using the default merge message","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2009-04-24T17:55:11Z","receivedAt":"2009-04-24T17:55:11Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Fri, Apr 24, 2009 at 01:50:57PM -0400, Caleb Cushing wrote:\n\n> On Fri, Apr 24, 2009 at 10:06 AM, Jeff King wrote:\n> > export GIT_EDITOR\n> >\n> maybe I'm being silly, but won't that then affect my interactive shells?\n\nNo, because you're putting it in your shell script, not in your .profile\n(right?). The \"export\" command just tells the shell \"pass this variable\nin the environment to any child processes you spawn\". Without it, the\nvariable is local to that shell.\n\n-Peff\n"}]}