{"thread":{"id":"10017","subject":"[PATCH] Remove 'submodules' from the TODO section of the User Manual.","startedAt":"2007-09-25T19:11:59Z","lastAt":"2007-09-26T20:37:36Z","messageCount":13,"participants":["Miklos Vajna","J. Bruce Fields","Johannes Schindelin"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"54024","messageId":"20070925191159.GG18370@genesis.frugalware.org","threadId":"10017","inReplyTo":null,"subject":"[PATCH] Remove 'submodules' from the TODO section of the User Manual.","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2007-09-25T19:11:59Z","receivedAt":"2007-09-25T19:11:59Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"A chapter about this topic has been added recently.\n\nSigned-off-by: Miklos Vajna \n---\n\ni forgot to include this change in my previous patch, so here is the\ncorrection.\n\n Documentation/user-manual.txt | 2 --\n 1 files changed, 0 insertions(+), 2 deletions(-)\n\ndiff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\nindex a085ca1..e4b04d0 100644\n--- a/Documentation/user-manual.txt\n+++ b/Documentation/user-manual.txt\n@@ -4277,5 +4277,3 @@ Write a chapter on using plumbing and writing scripts.\n Alternates, clone -reference, etc.\n \n git unpack-objects -r for recovery\n-\n-submodules\n-- \n1.5.3.2.80.g077d6f-dirty\n"},{"id":"54026","messageId":"20070925192315.GR30845@fieldses.org","threadId":"10017","inReplyTo":"20070925191159.GG18370@genesis.frugalware.org","subject":"Re: [PATCH] Remove 'submodules' from the TODO section of the User Manual.","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-09-25T19:23:15Z","receivedAt":"2007-09-25T19:23:15Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"On Tue, Sep 25, 2007 at 09:11:59PM +0200, Miklos Vajna wrote:\n> A chapter about this topic has been added recently.\n\nThanks, but it looks like Michael Smith already included this in his\nlatest patch:\n\n\thttp://marc.info/?l=git&m=119072428615724&w=2\n\n--b.\n"},{"id":"54031","messageId":"20070925194745.GI18370@genesis.frugalware.org","threadId":"10017","inReplyTo":"20070925192315.GR30845@fieldses.org","subject":"Re: [PATCH] Remove 'submodules' from the TODO section of the User Manual.","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2007-09-25T19:47:45Z","receivedAt":"2007-09-25T19:47:45Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Tue, Sep 25, 2007 at 03:23:15PM -0400, \"J. Bruce Fields\" wrote:\n> Thanks, but it looks like Michael Smith already included this in his\n> latest patch:\n> \n> \thttp://marc.info/?l=git&m=119072428615724&w=2\n\nah, my bad. i missed that. sorry for the noise :)\n\n- VMiklos\n"},{"id":"54032","messageId":"20070925194936.GU30845@fieldses.org","threadId":"10017","inReplyTo":"20070925194745.GI18370@genesis.frugalware.org","subject":"Re: [PATCH] Remove 'submodules' from the TODO section of the User Manual.","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-09-25T19:49:36Z","receivedAt":"2007-09-25T19:49:36Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"On Tue, Sep 25, 2007 at 09:47:45PM +0200, Miklos Vajna wrote:\n> On Tue, Sep 25, 2007 at 03:23:15PM -0400, \"J. Bruce Fields\" wrote:\n> > Thanks, but it looks like Michael Smith already included this in his\n> > latest patch:\n> > \n> > \thttp://marc.info/?l=git&m=119072428615724&w=2\n> \n> ah, my bad. i missed that. sorry for the noise :)\n\nNo problem.\n\nAnd there's a ton of other stuff on that todo list if you're looking to\nmake more \"noise\"--patches always welcomed....\n\n--b.\n"},{"id":"54036","messageId":"20070925195731.GJ18370@genesis.frugalware.org","threadId":"10017","inReplyTo":"20070925194936.GU30845@fieldses.org","subject":"Re: [PATCH] Remove 'submodules' from the TODO section of the User Manual.","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2007-09-25T19:57:31Z","receivedAt":"2007-09-25T19:57:31Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Tue, Sep 25, 2007 at 03:49:36PM -0400, \"J. Bruce Fields\" wrote:\n> And there's a ton of other stuff on that todo list if you're looking to\n> make more \"noise\"--patches always welcomed....\n\ni was this in the todo:\n\n\"Add a section on working with other version control systems, including\nCVS, Subversion, and just imports of series of release tarballs.\"\n\nto questions:\n\n1) does this include documentation about git-svn? i mean a howto similar\nto the submodules chapter.\n\n2) does it worth to document a typical usage of tailor? we used it a lot\nwhen converting from darcs to git and once you figure out the right\noptions, it's really easy to use it. but maybe it's unrelated.\n\nthanks,\n- VMiklos\n"},{"id":"54037","messageId":"20070925200252.GV30845@fieldses.org","threadId":"10017","inReplyTo":"20070925195731.GJ18370@genesis.frugalware.org","subject":"Re: [PATCH] Remove 'submodules' from the TODO section of the User Manual.","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-09-25T20:02:52Z","receivedAt":"2007-09-25T20:02:52Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"On Tue, Sep 25, 2007 at 09:57:31PM +0200, Miklos Vajna wrote:\n> i was this in the todo:\n> \n> \"Add a section on working with other version control systems, including\n> CVS, Subversion, and just imports of series of release tarballs.\"\n> \n> to questions:\n> \n> 1) does this include documentation about git-svn? i mean a howto similar\n> to the submodules chapter.\n\nCould be. Though when I used it I thought the git-svn manpage was\nactually very good, so I'd be tempted to just point to that.\n\n> 2) does it worth to document a typical usage of tailor? we used it a lot\n> when converting from darcs to git and once you figure out the right\n> options, it's really easy to use it. but maybe it's unrelated.\n\nI think we should try to keep the git documentation mostly confined to\ntools that are distributed with git itself. So it might be worth a few\nwords just to mention the existance of tailor and how it compares to\nother tools, but I'd leave it at that.\n\n--b.\n"},{"id":"54038","messageId":"20070925201306.GW30845@fieldses.org","threadId":"10017","inReplyTo":"20070925200252.GV30845@fieldses.org","subject":"Re: [PATCH] Remove 'submodules' from the TODO section of the User Manual.","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-09-25T20:13:06Z","receivedAt":"2007-09-25T20:13:06Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"On Tue, Sep 25, 2007 at 04:02:52PM -0400, bfields wrote:\n> I think we should try to keep the git documentation mostly confined to\n> tools that are distributed with git itself. So it might be worth a few\n> words just to mention the existance of tailor and how it compares to\n> other tools, but I'd leave it at that.\n\nSo in fact it might be that what's needed isn't any new documentation on\nthe available tools with their features and limitations.\n\nI know that when I recently had to deal with a svn tree the hardest part\nwas figuring out where to start (git-svn? git-svnimport?). I seem to\nrecall threads here suggesting this is a general problem.\n\nOne exception--the \"series of tarballs\" thing--I think it's cool that\nyou can just unpack a bunch of tarballs and string them together into a\ngit history. It gives a good sense of how git works, and I don't think\nit's documented explicitly anywhere. I think that might be kinda fun to\nwrite up. But I haven't tried.\n\n--b.\n"},{"id":"54039","messageId":"20070925201616.GX30845@fieldses.org","threadId":"10017","inReplyTo":"20070925201306.GW30845@fieldses.org","subject":"Re: [PATCH] Remove 'submodules' from the TODO section of the User Manual.","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-09-25T20:16:16Z","receivedAt":"2007-09-25T20:16:16Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"On Tue, Sep 25, 2007 at 04:13:06PM -0400, J. Bruce Fields wrote:\n> On Tue, Sep 25, 2007 at 04:02:52PM -0400, bfields wrote:\n> > I think we should try to keep the git documentation mostly confined to\n> > tools that are distributed with git itself. So it might be worth a few\n> > words just to mention the existance of tailor and how it compares to\n> > other tools, but I'd leave it at that.\n> \n> So in fact it might be that what's needed isn't any new documentation on\n> the available tools with their features and limitations.\n\n(Uh, I meant to say: \"isn't any new documentation on individual tools,\nbut rather a list of the available tools with their features and\nlimitations.\")\n\n> \n> I know that when I recently had to deal with a svn tree the hardest part\n> was figuring out where to start (git-svn? git-svnimport?). I seem to\n> recall threads here suggesting this is a general problem.\n> \n> One exception--the \"series of tarballs\" thing--I think it's cool that\n> you can just unpack a bunch of tarballs and string them together into a\n> git history. It gives a good sense of how git works, and I don't think\n> it's documented explicitly anywhere. I think that might be kinda fun to\n> write up. But I haven't tried.\n> \n> --b.\n> -\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at http://vger.kernel.org/majordomo-info.html\n"},{"id":"54051","messageId":"1190759824-18896-1-git-send-email-vmiklos@frugalware.org","threadId":"10017","inReplyTo":"20070925201306.GW30845@fieldses.org","subject":"[PATCH] User Manual: document import-tars.perl","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2007-09-25T22:37:04Z","receivedAt":"2007-09-25T22:37:04Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"Signed-off-by: Miklos Vajna \n---\n\nOn Tue, Sep 25, 2007 at 04:13:06PM -0400, \"J. Bruce Fields\" wrote:\n> One exception--the \"series of tarballs\" thing--I think it's cool that\n> you can just unpack a bunch of tarballs and string them together into a\n> git history. It gives a good sense of how git works, and I don't think\n> it's documented explicitly anywhere. I think that might be kinda fun to\n> write up. But I haven't tried.\n\nsomething like this?\n\nVMiklos\n\n Documentation/user-manual.txt | 13 +++++++++++++\n 1 files changed, 13 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\nindex a085ca1..f722932 100644\n--- a/Documentation/user-manual.txt\n+++ b/Documentation/user-manual.txt\n@@ -978,6 +978,19 @@ $ git add . # include everything below ./ in the first commit:\n $ git commit\n -------------------------------------------------\n \n+If you already have a series of tarballs (typically previous releases without\n+using a version control system):\n+\n+-------------------------------------------------\n+$ mkdir project\n+$ cd project\n+$ git init\n+$ perl import-tars.perl /path/to/tarballs/*.tar.bz2\n+$ git checkout import-tars\n+-------------------------------------------------\n+\n+You can find `import-tars.perl` in the `contrib/fast-import/` directory.\n+\n [[how-to-make-a-commit]]\n How to make a commit\n --------------------\n-- \n1.5.3.2.80.g077d6f-dirty\n"},{"id":"54107","messageId":"20070926181451.GA20976@fieldses.org","threadId":"10017","inReplyTo":"1190759824-18896-1-git-send-email-vmiklos@frugalware.org","subject":"Re: [PATCH] User Manual: document import-tars.perl","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-09-26T18:14:51Z","receivedAt":"2007-09-26T18:14:51Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"On Wed, Sep 26, 2007 at 12:37:04AM +0200, Miklos Vajna wrote:\n> Signed-off-by: Miklos Vajna \n> ---\n> \n> On Tue, Sep 25, 2007 at 04:13:06PM -0400, \"J. Bruce Fields\" wrote:\n> > One exception--the \"series of tarballs\" thing--I think it's cool that\n> > you can just unpack a bunch of tarballs and string them together into a\n> > git history. It gives a good sense of how git works, and I don't think\n> > it's documented explicitly anywhere. I think that might be kinda fun to\n> > write up. But I haven't tried.\n> \n> something like this?\n\nNeat-o, I'd missed (or forgotten about) import-tars.perl.\n\nBut I'd prefer to keep this first explanation of how to initialize and\ncommit to a new project pretty streamlined, and I don't think this is\nreally necessary here. So let's save this up until we have enough\nmaterial for a separate chapter or section on interacting with other\nscm's.\n\n--b.\n\n> \n> VMiklos\n> \n> Documentation/user-manual.txt | 13 +++++++++++++\n> 1 files changed, 13 insertions(+), 0 deletions(-)\n> \n> diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt\n> index a085ca1..f722932 100644\n> --- a/Documentation/user-manual.txt\n> +++ b/Documentation/user-manual.txt\n> @@ -978,6 +978,19 @@ $ git add . # include everything below ./ in the first commit:\n> $ git commit\n> -------------------------------------------------\n> \n> +If you already have a series of tarballs (typically previous releases without\n> +using a version control system):\n> +\n> +-------------------------------------------------\n> +$ mkdir project\n> +$ cd project\n> +$ git init\n> +$ perl import-tars.perl /path/to/tarballs/*.tar.bz2\n> +$ git checkout import-tars\n> +-------------------------------------------------\n> +\n> +You can find `import-tars.perl` in the `contrib/fast-import/` directory.\n> +\n> [[how-to-make-a-commit]]\n> How to make a commit\n> --------------------\n> -- \n> 1.5.3.2.80.g077d6f-dirty\n> \n"},{"id":"54108","messageId":"20070926182204.GB14959@genesis.frugalware.org","threadId":"10017","inReplyTo":"20070926181451.GA20976@fieldses.org","subject":"Re: [PATCH] User Manual: document import-tars.perl","fromName":"Miklos Vajna","fromEmail":"vmiklos@frugalware.org","sentAt":"2007-09-26T18:22:04Z","receivedAt":"2007-09-26T18:22:04Z","isPatch":true,"sender":{"key":"vmiklos@frugalware.org","avatar":"https://gravatar.com/avatar/401c1cbbb3a5d13e650c691a2c71d6fd0b80df1a01bc74d9f1972675dd58f2bd?d=mp&s=160"},"body":"On Wed, Sep 26, 2007 at 02:14:51PM -0400, \"J. Bruce Fields\" wrote:\n> Neat-o, I'd missed (or forgotten about) import-tars.perl.\n> \n> But I'd prefer to keep this first explanation of how to initialize and\n> commit to a new project pretty streamlined, and I don't think this is\n> really necessary here. So let's save this up until we have enough\n> material for a separate chapter or section on interacting with other\n> scm's.\n\nokay, now it's saved by gmane :)\n\n- VMiklos\n"},{"id":"54112","messageId":"Pine.LNX.4.64.0709262055210.28395@racer.site","threadId":"10017","inReplyTo":"20070926181451.GA20976@fieldses.org","subject":"Re: [PATCH] User Manual: document import-tars.perl","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-09-26T19:58:29Z","receivedAt":"2007-09-26T19:58:29Z","isPatch":true,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Wed, 26 Sep 2007, J. Bruce Fields wrote:\n\n> On Wed, Sep 26, 2007 at 12:37:04AM +0200, Miklos Vajna wrote:\n> > Signed-off-by: Miklos Vajna \n> > ---\n> > \n> > On Tue, Sep 25, 2007 at 04:13:06PM -0400, \"J. Bruce Fields\" wrote:\n> > > One exception--the \"series of tarballs\" thing--I think it's cool that\n> > > you can just unpack a bunch of tarballs and string them together into a\n> > > git history. It gives a good sense of how git works, and I don't think\n> > > it's documented explicitly anywhere. I think that might be kinda fun to\n> > > write up. But I haven't tried.\n> > \n> > something like this?\n> \n> Neat-o, I'd missed (or forgotten about) import-tars.perl.\n\nYou should also mention\n\n$ mkdir my-new-repo\n$ cd my-new-repo\n$ git init\n$ for z in /blub/*.zip\n do\n\trm -rf * 2> /dev/null &&\n\tunzip \"$z\" &&\n\tgit add . &&\n\tgit commit -m \"$z\" ||\n\tbreak\n done\n\nimport-tars.pl is much faster than this, of course, when it comes to tars, \nbut it has no clue about other archive formats.\n\nCiao,\nDscho\n"},{"id":"54116","messageId":"20070926203736.GC26099@fieldses.org","threadId":"10017","inReplyTo":"20070926182204.GB14959@genesis.frugalware.org","subject":"Re: [PATCH] User Manual: document import-tars.perl","fromName":"J. Bruce Fields","fromEmail":"bfields@fieldses.org","sentAt":"2007-09-26T20:37:36Z","receivedAt":"2007-09-26T20:37:36Z","isPatch":true,"sender":{"key":"bfields@citi.umich.edu","avatar":null},"body":"On Wed, Sep 26, 2007 at 08:22:04PM +0200, Miklos Vajna wrote:\n> On Wed, Sep 26, 2007 at 02:14:51PM -0400, \"J. Bruce Fields\" wrote:\n> > Neat-o, I'd missed (or forgotten about) import-tars.perl.\n> > \n> > But I'd prefer to keep this first explanation of how to initialize and\n> > commit to a new project pretty streamlined, and I don't think this is\n> > really necessary here. So let's save this up until we have enough\n> > material for a separate chapter or section on interacting with other\n> > scm's.\n> \n> okay, now it's saved by gmane :)\n\nAlso in my git tree--I took yours and Johannes' suggestions, put them in\na blender, and added a brief skeleton of a new chapter at:\n\n\tgit://linux-nfs.org/~bfields/git.git docwork-foreign-scms\n\n--b.\n"}]}