{"thread":{"id":"521","subject":"Re: [patch] add simple git documentation","startedAt":"2005-05-07T00:58:35Z","lastAt":"2005-05-08T07:35:56Z","messageCount":5,"participants":["Andrew Morton","David Greaves","Petr Baudis","Pavel Machek"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"2731","messageId":"20050506175835.65b9c9c1.akpm@osdl.org","threadId":"521","inReplyTo":"20050505102600.GA16387@elf.ucw.cz","subject":"Re: [patch] add simple git documentation","fromName":"Andrew Morton","fromEmail":"akpm@osdl.org","sentAt":"2005-05-07T00:58:35Z","receivedAt":"2005-05-07T00:58:35Z","isPatch":true,"sender":{"key":"akpm@osdl.org","avatar":null},"body":"Pavel Machek wrote:\n>\n> This adds short intro to git aimed at kernel hackers.\n> \n\nOK, but I'm hoping that shortly we'll have something more complete than\nthis, and your patch might not be a suitable starting point for that. \n(Large hint-dropping sounds).\n\n\n\n> \n> ---\n> commit addb0833bdadda14495d66749e6cb95b6a9445d7\n> tree 7e66cb899004fbec0fadae5c9265d0731d3a26f3\n> parent 1f9ca1262e6b27dde44d456a87c456d15f0a9b80\n> author 1115288688 +0200\n> committer 1115288688 +0200\n> \n> Index: Documentation/git.txt\n> ===================================================================\n> --- /dev/null (tree:de65e7579ed050d324357e3040b37c561676ab7d)\n> +++ 7e66cb899004fbec0fadae5c9265d0731d3a26f3/Documentation/git.txt (mode:100644 sha1:353d5ae7f46eeb79c058be611cb429622167f784)\n> @@ -0,0 +1,41 @@\n> +\tKernel hacker's guide to git\n> +\t~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n> + 2005 Pavel Machek \n> +\n> +You can get cogito at http://www.kernel.org/pub/software/scm/cogito/\n> +. Compile it, and place it somewhere in $PATH. Then you can get kernel\n> +by running\n> +\n> +mkdir clean-cg; cd clean-cg\n> +cg-init rsync://rsync.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git\n> +\n> +... Do cg-update origin to pickup latest changes from Linus. You can\n> +do cg-diff to see what changes you done in your local tree. cg-cancel\n> +will kill any such changes, and cg-commit will make them permanent.\n> +\n> +To get diff between your working tree and \"next tree up\", do cg-diff\n> +-r origin: . If you want to get the same diff but separated\n> +patch-by-patch, do cg-mkpatch origin: . If you want to pull changes\n> +from the \"up\" tree to your working tree, do cg-update origin.\n> +\n> +\n> +How to set up your trees so that you can cooperate with Linus\n> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n> +\n> +What I did:\n> +\n> +Created clean-cg. Initialized straight from Linus (as above). Then I\n> +created \"nice\" tree, good for Linus to pull from \n> +\n> +mkdir /data/l/linux-good; cd /data/l/linux-good\n> +cg-init /data/l/clean-cg\n> +\n> +and then my working tree, based on linux-good\n> +\n> +mkdir /data/l/linux-cg; cd /data/l/linux-cg\n> +cg-init /data/l/linux-good\n> +\n> +. I do my work in linux-cg. If someone sends me nice patch I should\n> +pass up, I apply it to linux-good with nice message and do\n> +\n> +cd /data/l/linux-cg; cg-update origin\n> \n> -- \n> Boycott Kodak -- for their patent abuse against Java.\n"},{"id":"2738","messageId":"427C7E38.3010301@dgreaves.com","threadId":"521","inReplyTo":"20050506175835.65b9c9c1.akpm@osdl.org","subject":"Re: [patch] add simple git documentation","fromName":"David Greaves","fromEmail":"david@dgreaves.com","sentAt":"2005-05-07T08:37:12Z","receivedAt":"2005-05-07T08:37:12Z","isPatch":true,"sender":{"key":"david@dgreaves.com","avatar":"https://gravatar.com/avatar/ca67bad50999edcdd137c9a65da2381557d175bea99ae956afdabc5785e42b79?d=mp&s=160"},"body":"Andrew Morton wrote:\n\n>Pavel Machek wrote:\n> \n>\n>>This adds short intro to git aimed at kernel hackers.\n>>\n>> \n>>\n>\n>OK, but I'm hoping that shortly we'll have something more complete than\n>this, and your patch might not be a suitable starting point for that. \n>(Large hint-dropping sounds).\n> \n>\nWhat are you looking for.\n\nFor man-page-a-like, have you seen Documentation/core-git.txt in Linus'\nrepository?\n\nI'll be working more on that this weekend.\n\nDavid\n\n-- \n\n"},{"id":"2744","messageId":"20050507113618.GA9495@pasky.ji.cz","threadId":"521","inReplyTo":"427C7E38.3010301@dgreaves.com","subject":"Re: [patch] add simple git documentation","fromName":"Petr Baudis","fromEmail":"pasky@ucw.cz","sentAt":"2005-05-07T11:36:18Z","receivedAt":"2005-05-07T11:36:18Z","isPatch":true,"sender":{"key":"pasky@ucw.cz","avatar":"https://avatars.githubusercontent.com/u/18439?v=4"},"body":"Dear diary, on Sat, May 07, 2005 at 10:37:12AM CEST, I got a letter\nwhere David Greaves told me that...\n> Andrew Morton wrote:\n> \n> >Pavel Machek wrote:\n> > \n> >\n> >>This adds short intro to git aimed at kernel hackers.\n> >>\n> >> \n> >>\n> >\n> >OK, but I'm hoping that shortly we'll have something more complete than\n> >this, and your patch might not be a suitable starting point for that. \n> >(Large hint-dropping sounds).\n> > \n> >\n> What are you looking for.\n> \n> For man-page-a-like, have you seen Documentation/core-git.txt in Linus'\n> repository?\n> \n> I'll be working more on that this weekend.\n\nAre you planning to split it to individual files at some point?\n\n(That's what I'd like to do with Documentation/cogito/, speaking of\nmanpageness...)\n\n-- \n\t\t\t\tPetr \"Pasky\" Baudis\nStuff: http://pasky.or.cz/\nC++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor\n"},{"id":"2754","messageId":"20050507195619.GB1907@elf.ucw.cz","threadId":"521","inReplyTo":"20050506175835.65b9c9c1.akpm@osdl.org","subject":"Re: [patch] add simple git documentation","fromName":"Pavel Machek","fromEmail":"pavel@ucw.cz","sentAt":"2005-05-07T19:56:19Z","receivedAt":"2005-05-07T19:56:19Z","isPatch":true,"sender":{"key":"pavel@ucw.cz","avatar":null},"body":"Hi!\n\n> > This adds short intro to git aimed at kernel hackers.\n> > \n> \n> OK, but I'm hoping that shortly we'll have something more complete than\n> this, and your patch might not be a suitable starting point for that. \n> (Large hint-dropping sounds).\n\nOkay.. Should I add Documentation/git, and put this as intro.txt into\nit?\n\n\t\t\t\t\t\t\t\tPavel\n\n-- \nBoycott Kodak -- for their patent abuse against Java.\n"},{"id":"2765","messageId":"427DC15C.3080208@dgreaves.com","threadId":"521","inReplyTo":"20050507113618.GA9495@pasky.ji.cz","subject":"Re: [patch] add simple git documentation","fromName":"David Greaves","fromEmail":"david@dgreaves.com","sentAt":"2005-05-08T07:35:56Z","receivedAt":"2005-05-08T07:35:56Z","isPatch":true,"sender":{"key":"david@dgreaves.com","avatar":"https://gravatar.com/avatar/ca67bad50999edcdd137c9a65da2381557d175bea99ae956afdabc5785e42b79?d=mp&s=160"},"body":"Petr Baudis wrote:\n\n>Dear diary, on Sat, May 07, 2005 at 10:37:12AM CEST, I got a letter\n>where David Greaves told me that...\n> \n>\n>>Andrew Morton wrote:\n>> \n>>\n>>>Pavel Machek wrote:\n>>> \n>>>\n>>>>This adds short intro to git aimed at kernel hackers.\n>>>> \n>>>>\n>>>OK, but I'm hoping that shortly we'll have something more complete than\n>>>this, and your patch might not be a suitable starting point for that. \n>>>(Large hint-dropping sounds).\n>>> \n>>>\n>>What are you looking for.\n>>\n>>For man-page-a-like, have you seen Documentation/core-git.txt in Linus'\n>>repository?\n>>\n>>I'll be working more on that this weekend.\n>> \n>>\n>Are you planning to split it to individual files at some point?\n> \n>\nYes. I'll see how using asciidoc affects that.\nAnd with Linus vacationing it looks like there'll be time this week.\n\n>(That's what I'd like to do with Documentation/cogito/, speaking of\n>manpageness...)\n> \n>\nOK\nBTW, whatever happened to perlification - the initial stab I sent you\nused the perl/pod approach.\nThe reason I ask is that that means the docs should/could be initially\nwritten as here-documents within the scripts rather than external manpages.\n\nDavid\n"}]}