{"thread":{"id":"4021","subject":"cg-mkpatch use case","startedAt":"2006-05-02T07:47:26Z","lastAt":"2006-05-02T22:34:38Z","messageCount":5,"participants":["Belmar-Letelier","Martin Langhoff","Petr Baudis"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"19352","messageId":"44570E8E.5070402@itaapy.com","threadId":"4021","inReplyTo":null,"subject":"cg-mkpatch use case","fromName":"Belmar-Letelier","fromEmail":"luis@itaapy.com","sentAt":"2006-05-02T07:47:26Z","receivedAt":"2006-05-02T07:47:26Z","isPatch":false,"sender":{"key":"luis@itaapy.com","avatar":null},"body":"Hello,\n\nI have 3 questions about cg-mkpatch\n\n1. I've receive a file \"xxx.patch\", this content came from\n cg-mkpatch, but I can't apply it.\n For example if I try git-am I get::\n\n $ git-am --signoff xxx.patch\n Patch does not have a valid e-mail address.\n\n What is the Cogito way to apply the result of \"cg-mkpatch\"\n\n\n2. What are the difference between usecases with \"cg-mkpatch\"\n and \"git-format-patch\" ?\n\n\n3. It seem that if a commit as a binary file they are no way to manage\n it by email patches. Any plan about this in Cogito ?\n\n\n-- \nLuis\n"},{"id":"19375","messageId":"46a038f90605021441t25152f7dtfed3828cd601b806@mail.gmail.com","threadId":"4021","inReplyTo":"44570E8E.5070402@itaapy.com","subject":"Re: cg-mkpatch use case","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2006-05-02T21:41:36Z","receivedAt":"2006-05-02T21:41:36Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"On 5/2/06, Belmar-Letelier wrote:\n> What is the Cogito way to apply the result of \"cg-mkpatch\"\n\nAFAIK, cg-patch. However, cg-mkpatch appeared before cg-patch, so you\nmay have a version of Cogito without cg-patch.\n\n> 2. What are the difference between usecases with \"cg-mkpatch\"\n> and \"git-format-patch\" ?\n\nIf you are familiar with git tools, use them instead of cg tools ;-)\n\nCg is simpler, so if you have relatively simple needs, or a team with\nsimple needs that doesn't need to know all the git tricks and\ninternals, it can be a timesaver. In my team, people start with Cg and\neventually evolve into using more and more of git.\n\ncheers,\n\n\nmartin\n"},{"id":"19379","messageId":"20060502215703.GK27689@pasky.or.cz","threadId":"4021","inReplyTo":"44570E8E.5070402@itaapy.com","subject":"Re: cg-mkpatch use case","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2006-05-02T21:57:03Z","receivedAt":"2006-05-02T21:57:03Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":" Hi,\n\nDear diary, on Tue, May 02, 2006 at 09:47:26AM CEST, I got a letter\nwhere Belmar-Letelier said that...\n> I have 3 questions about cg-mkpatch\n> \n> 1. I've receive a file \"xxx.patch\", this content came from\n> cg-mkpatch, but I can't apply it.\n> For example if I try git-am I get::\n> \n> $ git-am --signoff xxx.patch\n> Patch does not have a valid e-mail address.\n> \n> What is the Cogito way to apply the result of \"cg-mkpatch\"\n\n cg-mkpatch is a very old tool which has been long neglected and\nnot many people actually use it nowadays, I believe. You can apply it\nback using cg-patch (or even patch itself, or git-apply if you are\nlucky), but it won't automagically extract the commit message and\nauthorship information.\n\n> 2. What are the difference between usecases with \"cg-mkpatch\"\n> and \"git-format-patch\" ?\n\n git-format-patch outputs stuff in the mailbox format while cg-mkpatch\noutputs it in a more \"human readable\" (well, but quite historical)\nformat, but really, you probably want to use git-format-patch in almost\nevery case. In the (probably relatively near) future, cg-mkpatch might\nbecome merely a git-format-patch wrapper.\n\n> 3. It seem that if a commit as a binary file they are no way to manage\n> it by email patches. Any plan about this in Cogito ?\n\n Not any clear plans. I will welcome patches but it is not high\npriority for me currently.\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nRight now I am having amnesia and deja-vu at the same time. I think\nI have forgotten this before.\n"},{"id":"19380","messageId":"46a038f90605021519x5ee680b0v78dd5c092e1b191f@mail.gmail.com","threadId":"4021","inReplyTo":"20060502215703.GK27689@pasky.or.cz","subject":"Re: cg-mkpatch use case","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2006-05-02T22:19:00Z","receivedAt":"2006-05-02T22:19:00Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"On 5/3/06, Petr Baudis wrote:\n> not many people actually use it nowadays, I believe. You can apply it\n> back using cg-patch (or even patch itself, or git-apply if you are\n> lucky), but it won't automagically extract the commit message and\n> authorship information.\n\nErm... I don't personally use it, but cg-patch --long-help tells me...\n\n-c::\n Automatically extract the commit message and authorship information\n (if provided) from the patch and commit it after applying it\n successfuly.\n\nTruth in advertising? ;-)\n\ncheers,\n\n\nmartin\n"},{"id":"19381","messageId":"20060502223438.GH27631@pasky.or.cz","threadId":"4021","inReplyTo":"46a038f90605021519x5ee680b0v78dd5c092e1b191f@mail.gmail.com","subject":"Re: cg-mkpatch use case","fromName":"Petr Baudis","fromEmail":"pasky@suse.cz","sentAt":"2006-05-02T22:34:38Z","receivedAt":"2006-05-02T22:34:38Z","isPatch":false,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Wed, May 03, 2006 at 12:19:00AM CEST, I got a letter\nwhere Martin Langhoff said that...\n> On 5/3/06, Petr Baudis wrote:\n> >not many people actually use it nowadays, I believe. You can apply it\n> >back using cg-patch (or even patch itself, or git-apply if you are\n> >lucky), but it won't automagically extract the commit message and\n> >authorship information.\n> \n> Erm... I don't personally use it, but cg-patch --long-help tells me...\n> \n> -c::\n> Automatically extract the commit message and authorship information\n> (if provided) from the patch and commit it after applying it\n> successfuly.\n> \n> Truth in advertising? ;-)\n\nUhm, no, it just didn't stick in my mind in the storm of cg-patch\nimprovements. :-) Oops.\n\nSo, YES, there IS a way to apply cg-mkpatches preserving autorship and\neverything - cg-patch -c. Sorry for the confusion. ;-)\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nRight now I am having amnesia and deja-vu at the same time. I think\nI have forgotten this before.\n"}]}