{"thread":{"id":"30967","subject":"congif spec in GIT","startedAt":"2012-07-06T11:46:42Z","lastAt":"2012-07-07T18:28:16Z","messageCount":4,"participants":["Radu Manea","Neal Kreitzinger","Robin Rosenberg","Torsten Bögershausen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"194717","messageId":"4FF6D022.10801@itcnetworks.ro","threadId":"30967","inReplyTo":null,"subject":"congif spec in GIT","fromName":"Radu Manea","fromEmail":"rmanea@luxoft.com","sentAt":"2012-07-06T11:46:42Z","receivedAt":"2012-07-06T11:46:42Z","isPatch":false,"sender":{"key":"rmanea@luxoft.com","avatar":null},"body":"Hi,\n\nThank you for the detailed presentation posted on git.or.cz site.\n\nOne question: is there any equivalent config spec file for GIT as is in \nClearCase today?\n\nThanks,\nRadu M.\n+40 21 203 6611\n"},{"id":"194725","messageId":"4FF70A6C.5010605@gmail.com","threadId":"30967","inReplyTo":"4FF6D022.10801@itcnetworks.ro","subject":"Re: congif spec in GIT","fromName":"Neal Kreitzinger","fromEmail":"nkreitzinger@gmail.com","sentAt":"2012-07-06T15:55:24Z","receivedAt":"2012-07-06T15:55:24Z","isPatch":false,"sender":{"key":"nkreitzinger@gmail.com","avatar":null},"body":"On 7/6/2012 6:46 AM, Radu Manea wrote:\n>\n> Thank you for the detailed presentation posted on git.or.cz site.\n>\n> One question: is there any equivalent config spec file for GIT as is in\n> ClearCase today?\n>\nI don't know clearcase, but have you looked at git-config manpage?\nhttp://git-htmldocs.googlecode.com/git/git-config.html\n\nv/r,\nneal\n"},{"id":"194768","messageId":"4FF8071B.6010407@dewire.com","threadId":"30967","inReplyTo":"4FF6D022.10801@itcnetworks.ro","subject":"Re: congif spec in GIT","fromName":"Robin Rosenberg","fromEmail":"robin.rosenberg.lists@dewire.com","sentAt":"2012-07-07T09:53:31Z","receivedAt":"2012-07-07T09:53:31Z","isPatch":false,"sender":{"key":"robin.rosenberg@dewire.com","avatar":"https://avatars.githubusercontent.com/u/46357?v=4"},"body":"Radu Manea skrev 2012-07-06 13.46:\n> Hi,\n>\n> Thank you for the detailed presentation posted on git.or.cz site.\n>\n> One question: is there any equivalent config spec file for GIT as is in ClearCase today?\n\nRepo (http://source.android.com/source/version-control.html) is perhaps\nthe tool that is most similar in functionality to the config spec. It allows you\nto perform operations over multiple repositories.\n\n-- robin\n"},{"id":"194771","messageId":"4FF87FC0.2080900@web.de","threadId":"30967","inReplyTo":"4FF6D022.10801@itcnetworks.ro","subject":"Re: congif spec in GIT","fromName":"Torsten Bögershausen","fromEmail":"tboegi@web.de","sentAt":"2012-07-07T18:28:16Z","receivedAt":"2012-07-07T18:28:16Z","isPatch":false,"sender":{"key":"tboegi@web.de","avatar":"https://avatars.githubusercontent.com/u/7138363?v=4"},"body":"On 06.07.12 13:46, Radu Manea wrote:\n> Hi,\n>\n> Thank you for the detailed presentation posted on git.or.cz site.\n>\n> One question: is there any equivalent config spec file for GIT as is in ClearCase today?\n\nThere are similarities, and differences between git and ClearCase,\nI can only point out the very basic differences,\nbecause the philosophy of these 2 tools is completely different.\n\n\nCC has a \"virtual file system\", often mounted on /vobs on Unix,\nand M:\\ (or another drive name) on Windows.\n\nCC simulates a file system, where files are seen according\nto the config spec. Changing the config spec will change the\nversion of the files seen under /vobs immediately.\n\nIf you want a copy of all the files on your local disk,\nyou need to create a \"snapshot view\". After changing\nthe config spec, the snapshot view needs to be updated.\n\ngit always has a \"working tree\", similar to a \"snapshot view\"\n(except for \"bare repositories\", they correspond to a CC server)\n\n\nCC uses branches\ngit uses branches\n\nCC uses labels\ngit uses commit ids, A tag may point to a commit id\n\nCC defines for each file/directory which label is used\n    When a file is checked out, a branch is created for that file element\n   different directories may use different branches\n- git uses the same branch for the whole repo\n\nCC uses labels for each directory, whatever the config spec say for that \nvery directory.\n- git uses a commit id as a base for that branch.\n\n\nSo if try to transform \"a branch in git\" into a config spec,\nwe do:\n\n$ git status\n# On branch my_feature_branch\n  (and that branch is defined on the whole working tree, similar to \n/vobs/projects/git/tb)\n\nIf I open the \"engine bonnet\" of git, to see what that means \ntechnically, I run on the command line:\n\n$ cat .git/HEAD ref: refs/heads/my_feature_branch\n(we are on branch my_feature_branch)\n\nWhen I dig further:\n\n$ cat .git/refs/heads/my_feature_branch\na5b0a8ff7f48cfd5ea19712680c64a029e99c2ba\n\nWe see that my branch is taking commit a5b08ff7 as a base line\n\n\nSo a \"config spec\" could include 3 lines, kind of\n\"all files are CHECKOUT/CHECKIN\"\n\"All files are based on commit id a5b0a8ff7f48cfd5ea19712680c64a029e99c2ba\"\n\"If you commit one or more files at once, they are recorded on branch \n\"my_feature_branch\"\n\nHTH\n/Torsten\n"}]}