{"thread":{"id":"1560","subject":"Re: git-format-patch + git-applymbox small issue","startedAt":"2005-08-17T17:54:51Z","lastAt":"2005-08-17T19:55:47Z","messageCount":4,"participants":["Marco Costalba","Junio C Hamano","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"7455","messageId":"20050817175452.84541.qmail@web26306.mail.ukl.yahoo.com","threadId":"1560","inReplyTo":null,"subject":"Re: git-format-patch + git-applymbox small issue","fromName":"Marco Costalba","fromEmail":"mcostalba@yahoo.it","sentAt":"2005-08-17T17:54:51Z","receivedAt":"2005-08-17T17:54:51Z","isPatch":false,"sender":{"key":"mcostalba@gmail.com","avatar":null},"body":"Johannes Schindelin wrote:\n\n>Hi,\n>\n>On Wed, 17 Aug 2005, Marco Costalba wrote:\n>\n>>P.S: I say 'revision', and 'git archive' but are very common also \n>>'commit' and 'git repository'. This is just a silly example where a \n>>common dictionary should be useful.\n>\n>\n>How about the glossary, which I posted a few hours ago?\n>\n>Ciao,\n>Dscho\n>\n>\n\nYeah, I missed it.\n\nSorry for the noise.\n\nBy the way, a very good and useful job.\n\n>\n>revision::\n>\tA particular state of files and directories which was stored in\n>\tthe object database. It is referenced by a commit object.\n>\n\n\n>\n>commit object::\n>\tAn object which contains the information about a particular\n>\trevision, such as parents, committer, author, date and the\n>\ttree object which corresponds to the top directory of the\n>\tstored revision.\n>\n\nSo 'revision' is the struct and 'commit object' the pointer ;-)\n\n\n\n>\n>repository::\n>\tA collection of refs together with an object database containing\n>\tall objects, which are reachable from the refs. A repository can\n>\tshare an object database with other repositories.\n>\n\nIn a lot of git documentation, starting from the tutorial, it is used 'git archive' \nbut peraphs 'repository' is more a standard definition for an SCM archive. \nJust archive peraphs is too generic, also a tarball is an archive :-)\n\nMarco\n\n\n__________________________________________________\nDo You Yahoo!?\nTired of spam?  Yahoo! Mail has the best spam protection around \nhttp://mail.yahoo.com \n"},{"id":"7459","messageId":"7vll30wejs.fsf@assigned-by-dhcp.cox.net","threadId":"1560","inReplyTo":"20050817175452.84541.qmail@web26306.mail.ukl.yahoo.com","subject":"Re: git-format-patch + git-applymbox small issue","fromName":"Junio C Hamano","fromEmail":"junkio@cox.net","sentAt":"2005-08-17T19:26:15Z","receivedAt":"2005-08-17T19:26:15Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Marco Costalba <mcostalba@yahoo.it> writes:\n\n>>revision::\n>>\tA particular state of files and directories which was stored in\n>>\tthe object database. It is referenced by a commit object.\n>>\n>>commit object::\n>>\tAn object which contains the information about a particular\n>>\trevision, such as parents, committer, author, date and the\n>>\ttree object which corresponds to the top directory of the\n>>\tstored revision.\n> So 'revision' is the struct and 'commit object' the pointer ;-)\n\nIt would be more like \"revision\" is a concept represented (not\n\"referenced\") by a commit object.\n\n>>repository::\n>>\tA collection of refs together with an object database containing\n>>\tall objects, which are reachable from the refs. A repository can\n>>\tshare an object database with other repositories.\n>>\n>\n> In a lot of git documentation, starting from the tutorial, it is used 'git archive' \n> but peraphs 'repository' is more a standard definition for an SCM archive. \n> Just archive peraphs is too generic, also a tarball is an archive :-)\n\nAgreed.  I personally think the word \"archive\" on this list came\nfrom people who have some degree of tla background.  CVS and SVN\npeople would have said repository.\n"},{"id":"7463","messageId":"Pine.LNX.4.63.0508172151390.17234@wgmdd8.biozentrum.uni-wuerzburg.de","threadId":"1560","inReplyTo":"7vll30wejs.fsf@assigned-by-dhcp.cox.net","subject":"Re: git-format-patch + git-applymbox small issue","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2005-08-17T19:53:15Z","receivedAt":"2005-08-17T19:53:15Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Wed, 17 Aug 2005, Junio C Hamano wrote:\n\n> Marco Costalba <mcostalba@yahoo.it> writes:\n> \n> > So 'revision' is the struct and 'commit object' the pointer ;-)\n> \n> It would be more like \"revision\" is a concept represented (not\n> \"referenced\") by a commit object.\n\nActually, I think it is \"referenced\", because the commit object contains a \nlittle metadata, and then only refs (pointers).\n\n> Agreed.  I personally think the word \"archive\" on this list came\n> from people who have some degree of tla background.  CVS and SVN\n> people would have said repository.\n\nI'll add it anyway.\n\nCiao,\nDscho\n"},{"id":"7464","messageId":"Pine.LNX.4.63.0508172153320.17234@wgmdd8.biozentrum.uni-wuerzburg.de","threadId":"1560","inReplyTo":"20050817175452.84541.qmail@web26306.mail.ukl.yahoo.com","subject":"Re: git-format-patch + git-applymbox small issue","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2005-08-17T19:55:47Z","receivedAt":"2005-08-17T19:55:47Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Wed, 17 Aug 2005, Marco Costalba wrote:\n\n> Johannes Schindelin wrote:\n> \n> > [...]\n> >\n> By the way, a very good and useful job.\n\nThank you! While I think it is one of the less-fun and less-think jobs, it \nmight be good to have it for people o look it up all the time.\n\n> So 'revision' is the struct and 'commit object' the pointer ;-)\n\nAs I said in another mail: Yes!\n\nCiao,\nDscho\n"}]}