{"thread":{"id":"4779","subject":"Why's Git called Git ?","startedAt":"2006-07-06T02:18:12Z","lastAt":"2006-07-07T18:40:07Z","messageCount":2,"participants":["Aaron Gray","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"23297","messageId":"01f201c6a0a2$6faa0f80$0200a8c0@AMD2500","threadId":"4779","inReplyTo":null,"subject":"Why's Git called Git ?","fromName":"Aaron Gray","fromEmail":"angray@beeb.net","sentAt":"2006-07-06T02:18:12Z","receivedAt":"2006-07-06T02:18:12Z","isPatch":false,"sender":{"key":"angray@beeb.net","avatar":null},"body":">> I am toying with using a VCS for a set of related projects, either CVS\n>> because its well known, SubVersion for ease of use, or Git as it is new.\n>> Lots to descide upon, any pointers would be appreciated.\n>\n> CVS is showing it's age; mainly the fact that IIRC it began as a series of\n> scripts over RCS, file level version control system, extending version\n> control to sets of files, somewhat. Branching in CVS is serious PITA.\n> Renaming _with_ retaining full and correct history: forget about it.\n\nOkay, we like branching and forking.\n\n> Subversion is \"better CVS\": still centralized, CVS infernal branching\n> replaced by \"cheap copy\" branching. Well known, replaces CVS thorough OSS\n> projects.\n\nOkay.\n\n> Git, Mercurial, Monotone, Bazaar-NG, Darcs are new brand of distributed \n> VCS.\n> I really like notion of branching in Git; but be warned about tracking and\n> not recording renames, and the need of explicit packing (the latter very\n> minor). Powerfull, perhaps too powerfull for newbie user: but that is what\n> Cogito is for (although now Git contains fairly large set of high-level\n> commands).\n\nWe like to move forward.\n\n>\n>  http://git.or.cz/\n>  http://git.or.cz/gitwiki\n>  http://git.or.cz/gitwiki/Git\n> and \"Other version control software\" at\n>  http://git.or.cz/gitwiki/GitLinks\n\n\nYes, been there, thanks though.\n\n> P.S. If you decide to use Git as VCS for your project, consider adding \n> entry\n> about it on http://git.or.cz/gitwiki/GitProjects wiki page.\n\nLooks like I maybe doing a preliminary Windows Git HOWTO on the GitWiki, if \nno one else has trod this ground :) (Might need some proper help testing \nthough)\n\nThanks,\n\nAaron\n"},{"id":"23381","messageId":"e8m9pl$m37$2@sea.gmane.org","threadId":"4779","inReplyTo":"01f201c6a0a2$6faa0f80$0200a8c0@AMD2500","subject":"Re: Why's Git called Git ?","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2006-07-07T18:40:07Z","receivedAt":"2006-07-07T18:40:07Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Aaron Gray wrote:\n\n>> I really like notion of branching in Git; but be warned about tracking and\n>> not recording renames, and the need of explicit packing (the latter very\n>> minor). Powerfull, perhaps too powerfull for newbie user: but that is what\n>> Cogito is for (although now Git contains fairly large set of high-level\n>> commands).\n> \n> We like to move forward.\n\nWhat I like a lot in Git is very easy switching of working area between \nbranches, and to arbitrary commit (point in history).\n\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"}]}