{"thread":{"id":"13320","subject":"help with git usage","startedAt":"2008-04-29T17:37:32Z","lastAt":"2008-05-08T23:07:10Z","messageCount":12,"participants":["Daniel Quinlan","Daniel Barkalow","Jakub Narebski","Richard Quirk","Matt Graham","Andreas Ericsson","Julian Phillips","Dirk Süsserott"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"75552","messageId":"200804291738.m3THc2hC030601@rs40.luxsci.com","threadId":"13320","inReplyTo":null,"subject":"help with git usage","fromName":"Daniel Quinlan","fromEmail":"danq@brtt.com","sentAt":"2008-04-29T17:37:32Z","receivedAt":"2008-04-29T17:37:32Z","isPatch":false,"sender":{"key":"danq@brtt.com","avatar":null},"body":"I've been trying to use git for awhile now, (and I've read a lot of \ndocumentation, though maybe my\ncomprehension has not been high enough) but there are several \noperations which I\ncan't figure out:\n\n1) After cloning a repository from work at home, making some changes \nand committing them,\nI use \"git push\" to push them back to the work repository. The \nchanges seem to make it to the\nwork repository (I see the commit message in git log), but I can't \nfigure out how to get the\nchanges into the working set at work. (evidently not merge, checkout \nor reset -- seems like it\nshould be merge, but)\n\n2) I can't figure out how to get back the latest (or any other) \nversion of a file I've modified (or deleted)\nin the working set. (Well, I suppose I could checkout the whole tree \nsomewhere else and copy the\nrelevant file, but I'm hoping there's something simpler).\n\n3) Similarly, I can't use the little context diffs I can see in git- \ngui -- I need to see side by side comparisons;\nI've become accustomed to tkdiff. It seems like git mergetool knows \nhow to do that in some restricted\ncircumstances, but I want to do it outside the context of a merge.\n\nThanks,\n-- danq\n"},{"id":"75557","messageId":"alpine.LNX.1.00.0804291354070.19665@iabervon.org","threadId":"13320","inReplyTo":"200804291738.m3THc2hC030601@rs40.luxsci.com","subject":"Re: help with git usage","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2008-04-29T18:07:14Z","receivedAt":"2008-04-29T18:07:14Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"On Tue, 29 Apr 2008, Daniel Quinlan wrote:\n\n> I've been trying to use git for awhile now, (and I've read a lot of\n> documentation, though maybe my\n> comprehension has not been high enough) but there are several operations which\n> I\n> can't figure out:\n> \n> 1) After cloning a repository from work at home, making some changes and\n> committing them,\n> I use \"git push\" to push them back to the work repository. The changes seem\n> to make it to the\n> work repository (I see the commit message in git log), but I can't figure out\n> how to get the\n> changes into the working set at work. (evidently not merge, checkout or reset\n> -- seems like it\n> should be merge, but)\n\nYou shouldn't push to a non-bare repository. You should, instead, set up a \nbare repository for publishing your changes, and have all of the \nrepositories you work in be clones of that. The issue is that git doesn't \nexpect something outside of the repository to change the current branch \n(much like CVS doesn't expect something else to update CVS/Entries in your \nworking directory). Another alternative is, from home, to do:\n\n$ git push origin refs/heads/*:refs/remotes/home/*\n\nThen, at work, you can do:\n\n$ git merge home/master\n\n> 2) I can't figure out how to get back the latest (or any other) version of a\n> file I've modified (or deleted)\n> in the working set. (Well, I suppose I could checkout the whole tree\n> somewhere else and copy the\n> relevant file, but I'm hoping there's something simpler).\n\n$ git checkout HEAD -- \n\n(And you can use any commit instead of HEAD to get other versions)\n\n> 3) Similarly, I can't use the little context diffs I can see in git-gui -- I\n> need to see side by side comparisons;\n> I've become accustomed to tkdiff. It seems like git mergetool knows how to do\n> that in some restricted\n> circumstances, but I want to do it outside the context of a merge.\n\nThis I don't know, but you can get particular files from particular \ncommits output with \"git show :\", and you can likely wire \nsomething up.\n\n\t-Daniel\n*This .sig left intentionally blank*\n"},{"id":"75648","messageId":"m3tzhjokox.fsf@localhost.localdomain","threadId":"13320","inReplyTo":"alpine.LNX.1.00.0804291354070.19665@iabervon.org","subject":"Re: help with git usage","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2008-04-30T07:39:52Z","receivedAt":"2008-04-30T07:39:52Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Daniel Barkalow writes:\n\n> On Tue, 29 Apr 2008, Daniel Quinlan wrote:\n>\n> > I've been trying to use git for awhile now, (and I've read a lot\n> > of documentation, though maybe my comprehension has not been high\n> > enough) but there are several operations which I can't figure out:\n\nMany of answers to your questions can be found on GitFaq,\nhttp://git.or.cz/gitwiki/GitFaq\n \n> > 1) After cloning a repository from work at home, making some\n> > changes and committing them, I use \"git push\" to push them back to\n> > the work repository. The changes seem to make it to the work\n> > repository (I see the commit message in git log), but I can't\n> > figure out how to get the changes into the working set at work.\n> > (evidently not merge, checkout or reset -- seems like it should be\n> > merge, but)\n\nWhat do you mean that reset doesn't work? \"git reset --hard HEAD\"\nshould update index and working tree, even if someone has updated\nHEAD behingd git's back ;-) NOTE, NOTE, NOTE: this is not a correct\nsolution.\n\n> You shouldn't push to a non-bare repository. You should, instead, set up a \n> bare repository for publishing your changes, and have all of the \n> repositories you work in be clones of that. The issue is that git doesn't \n> expect something outside of the repository to change the current branch \n> (much like CVS doesn't expect something else to update CVS/Entries in your \n> working directory). Another alternative is, from home, to do:\n> \n> $ git push origin refs/heads/*:refs/remotes/home/*\n> \n> Then, at work, you can do:\n> \n> $ git merge home/master\n\nAnd yet another alternative is, if possible, to always use \"git pull\"\n(or \"git fetch\").\n\nSee also \"Why won't I see changes in the remote repo after \"git push\"?\"\nhttp://git.or.cz/gitwiki/GitFaq#head-b96f48bc9c925074be9f95c0fce69bcece5f6e73\nand \"How would I use 'git push' to sync out of a firewalled host?\"\nhttp://git.or.cz/gitwiki/GitFaq#head-46de97a5ac549d3adf406c22674b3325ae25d09c\n\n> > 2) I can't figure out how to get back the latest (or any other)\n> > version of a file I've modified (or deleted) in the working set.\n> > (Well, I suppose I could checkout the whole tree somewhere else\n> > and copy the relevant file, but I'm hoping there's something\n> > simpler).\n>\n> $ git checkout HEAD -- \n> \n> (And you can use any commit instead of HEAD to get other versions)\n\nSee also \"How to revert file to version from current commit?\"\nhttp://git.or.cz/gitwiki/GitFaq#head-f2ac5ecb3db6c54e9977bf969c0456091ac332a3\n \n> > 3) Similarly, I can't use the little context diffs I can see in\n> > git-gui -- I need to see side by side comparisons; I've become\n> > accustomed to tkdiff. It seems like git mergetool knows how to do\n> > that in some restricted circumstances, but I want to do it outside\n> > the context of a merge.\n> \n> This I don't know, but you can get particular files from particular \n> commits output with \"git show :\", and you can likely wire \n> something up.\n\nTkDiff doesn't have support for Git, although I think it wouldn't be\nthat hard to add. Tkere is Google Summer of Code project to add DVCS\nsupport, with Git as first example DVCS supported, to KDevelop so\nperhaps KDiff3 would learn Git support.\n\n>From the various graphical comparison tools, Meld has supposedly Git\nsupport (http://meld.sourceforge.net/). Supposedly only because I\nhave not tested this; see\nhttp://git.or.cz/gitwiki/InterfacesFrontendsAndTools#head-00fbd1ac45fe93dac4653cad3639b3df73d8657e\n\nBTW. I'm working in my spare time to add side-by-side diff, based on\nTkDiff actually, to git-gui.\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"},{"id":"75650","messageId":"cac9e4380804300122v4f23251cqbc36640a07379c8@mail.gmail.com","threadId":"13320","inReplyTo":"200804291738.m3THc2hC030601@rs40.luxsci.com","subject":"Re: help with git usage","fromName":"Richard Quirk","fromEmail":"richard.quirk@gmail.com","sentAt":"2008-04-30T08:22:29Z","receivedAt":"2008-04-30T08:22:29Z","isPatch":false,"sender":{"key":"richard.quirk@gmail.com","avatar":null},"body":"On Tue, Apr 29, 2008 at 7:37 PM, Daniel Quinlan wrote:\n\n> 3) Similarly, I can't use the little context diffs I can see in git-gui --\n> I need to see side by side comparisons;\n> I've become accustomed to tkdiff. It seems like git mergetool knows how to\n> do that in some restricted\n> circumstances, but I want to do it outside the context of a merge.\n\nIf you use Vim, I'd recommend the vcscommand plugin - see\nhttp://code.google.com/p/vcscommand/ - which has fairly recently added\ngit support. Once installed :VCSVimDiff shows the diff side by side\nbetween working copy and HEAD (by default, or whatever revision you\ntell it) like a regular vimdiff between files.\n"},{"id":"75669","messageId":"m3hcdjocdc.fsf@localhost.localdomain","threadId":"13320","inReplyTo":"cac9e4380804300122v4f23251cqbc36640a07379c8@mail.gmail.com","subject":"Re: help with git usage","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2008-04-30T10:39:34Z","receivedAt":"2008-04-30T10:39:34Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"\"Richard Quirk\" writes:\n\n> On Tue, Apr 29, 2008 at 7:37 PM, Daniel Quinlan wrote:\n> \n>> 3) Similarly, I can't use the little context diffs I can see in\n>> git-gui -- I need to see side by side comparisons; I've become\n>> accustomed to tkdiff. It seems like git mergetool knows how to do\n>> that in some restricted circumstances, but I want to do it outside\n>> the context of a merge.\n> \n> If you use Vim, I'd recommend the vcscommand plugin - see\n> http://code.google.com/p/vcscommand/ - which has fairly recently added\n> git support. Once installed :VCSVimDiff shows the diff side by side\n> between working copy and HEAD (by default, or whatever revision you\n> tell it) like a regular vimdiff between files.\n\nCould you add infomration about this to Git Wiki\n http://git.or.cz/gitwiki/InterfacesFrontendsAndTools\nsomewhere in \"Editors and IDE integration\" subsection?\n\nTIA\n-- \nJakub Narebski\nGNU Emacs user\n"},{"id":"75671","messageId":"cac9e4380804300450k763fa22dr19260b2c75f11c96@mail.gmail.com","threadId":"13320","inReplyTo":"m3hcdjocdc.fsf@localhost.localdomain","subject":"Re: help with git usage","fromName":"Richard Quirk","fromEmail":"richard.quirk@gmail.com","sentAt":"2008-04-30T11:50:45Z","receivedAt":"2008-04-30T11:50:45Z","isPatch":false,"sender":{"key":"richard.quirk@gmail.com","avatar":null},"body":"On Wed, Apr 30, 2008 at 12:39 PM, Jakub Narebski wrote:\n>\n> > If you use Vim, I'd recommend the vcscommand plugin - see\n> > http://code.google.com/p/vcscommand/\n>\n> Could you add infomration about this to Git Wiki\n>\n> http://git.or.cz/gitwiki/InterfacesFrontendsAndTools\n> somewhere in \"Editors and IDE integration\" subsection?\n>\n\nCertainly. I've added a note about it to the end of that section.\n"},{"id":"75673","messageId":"1c5969370804300502obbc5a63v4c2c1a1175084237@mail.gmail.com","threadId":"13320","inReplyTo":"alpine.LNX.1.00.0804291354070.19665@iabervon.org","subject":"Re: help with git usage","fromName":"Matt Graham","fromEmail":"mdg149@gmail.com","sentAt":"2008-04-30T12:02:05Z","receivedAt":"2008-04-30T12:02:05Z","isPatch":false,"sender":{"key":"mdg149@gmail.com","avatar":"https://gravatar.com/avatar/a1f130a60a6550f75e8d7d3849e58e46494f36bfaf764a38cfd695ac85de8576?d=mp&s=160"},"body":"On Tue, Apr 29, 2008 at 2:07 PM, Daniel Barkalow wrote:\n> On Tue, 29 Apr 2008, Daniel Quinlan wrote:\n>\n> > I've been trying to use git for awhile now, (and I've read a lot of\n> > documentation, though maybe my\n> > comprehension has not been high enough) but there are several operations which\n> > I\n> > can't figure out:\n> >\n> > 1) After cloning a repository from work at home, making some changes and\n> > committing them,\n> > I use \"git push\" to push them back to the work repository. The changes seem\n> > to make it to the\n> > work repository (I see the commit message in git log), but I can't figure out\n> > how to get the\n> > changes into the working set at work. (evidently not merge, checkout or reset\n> > -- seems like it\n> > should be merge, but)\n>\n> You shouldn't push to a non-bare repository.\n\nIs there any reason it wouldn't be appropriate to make git refuse to\npush to non-bare repositories?\n"},{"id":"75680","messageId":"48186F97.6080509@op5.se","threadId":"13320","inReplyTo":"1c5969370804300502obbc5a63v4c2c1a1175084237@mail.gmail.com","subject":"Re: help with git usage","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2008-04-30T13:09:43Z","receivedAt":"2008-04-30T13:09:43Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"Matt Graham wrote:\n> On Tue, Apr 29, 2008 at 2:07 PM, Daniel Barkalow wrote:\n>> On Tue, 29 Apr 2008, Daniel Quinlan wrote:\n>>\n>> > I've been trying to use git for awhile now, (and I've read a lot of\n>> > documentation, though maybe my\n>> > comprehension has not been high enough) but there are several operations which\n>> > I\n>> > can't figure out:\n>> >\n>> > 1) After cloning a repository from work at home, making some changes and\n>> > committing them,\n>> > I use \"git push\" to push them back to the work repository. The changes seem\n>> > to make it to the\n>> > work repository (I see the commit message in git log), but I can't figure out\n>> > how to get the\n>> > changes into the working set at work. (evidently not merge, checkout or reset\n>> > -- seems like it\n>> > should be merge, but)\n>>\n>> You shouldn't push to a non-bare repository.\n> \n> Is there any reason it wouldn't be appropriate to make git refuse to\n> push to non-bare repositories?\n\n\nIt has several very valid uses. Newcomers who don't know what happens are\noften better off not doing it, which is why it's not recommended. Making\ngit refuse would prevent the valid uses altogether though.\n\n-- \nAndreas Ericsson andreas.ericsson@op5.se\nOP5 AB www.op5.se\nTel: +46 8-230225 Fax: +46 8-230231\n"},{"id":"76333","messageId":"200805072242.m47Mg1o0015578@rs40.luxsci.com","threadId":"13320","inReplyTo":"m3tzhjokox.fsf@localhost.localdomain","subject":"Re: help with git usage","fromName":"Daniel Quinlan","fromEmail":"danq@brtt.com","sentAt":"2008-05-07T22:41:27Z","receivedAt":"2008-05-07T22:41:27Z","isPatch":false,"sender":{"key":"danq@brtt.com","avatar":null},"body":"Thanks for your earlier responses, they were very helpful.\n\nOn Apr 30, 2008, at 1:39 AM, Jakub Narebski wrote:\n\n> Daniel Barkalow writes:\n>\n>> On Tue, 29 Apr 2008, Daniel Quinlan wrote:\n>>\n>>> I've been trying to use git for awhile now, (and I've read a lot\n>>> of documentation, though maybe my comprehension has not been high\n>>> enough) but there are several operations which I can't figure out:\n>\n> Many of answers to your questions can be found on GitFaq,\n> http://git.or.cz/gitwiki/GitFaq\n\nI should have read this earlier. I don't really understand the\ndetails, but I get the idea: make the central repository bare.\n\n>\n\n>>> 3) Similarly, I can't use the little context diffs I can see in\n>>> git-gui -- I need to see side by side comparisons; I've become\n>>> accustomed to tkdiff. It seems like git mergetool knows how to do\n>>> that in some restricted circumstances, but I want to do it outside\n>>> the context of a merge.\n>>\n>> This I don't know, but you can get particular files from particular\n>> commits output with \"git show :\", and you can likely \n>> wire\n>> something up.\n>\n> From the various graphical comparison tools, Meld has supposedly Git\n> support (http://meld.sourceforge.net/). Supposedly only because I\n> have not tested this; see\n> http://git.or.cz/gitwiki/InterfacesFrontendsAndTools#head-00fbd1ac45fe93dac4653cad3639b3df73d8657e\n>\n\nI found no mention of git on the meld man page or in the meld mailing \nlist.\n\nHere's a (perhaps naive) perl script which uses \"git show\" and wraps \naround\nthe original tkdiff. Other cvs users might find it useful, though it \ncan surely\nbe improved.\n\n\n\n\n\n\n\nI'm looking for a way to embed some identifying information about \nversion\ninto compiled programs. I hasten to add that I am not looking to \nexpand RCS-like\ntags. Unlike CVS/RCS, git provides a single value that characterizes \nthe whole\ndistribution, at least if everything is committed. So, something like \n\"git log | head -1 | awk '{print $2}'\"\nprobably provides a value which I can embed into executables and \nlibraries, tying\nthem to a particular source configuration. I'm just curious if \nthere's a better approach\nto getting the commit hash.\n\n-- danq\n\n\n"},{"id":"76369","messageId":"Pine.LNX.4.64.0805080112580.6421@kaos.quantumfyre.co.uk","threadId":"13320","inReplyTo":"200805072242.m47Mg1o0015578@rs40.luxsci.com","subject":"Re: help with git usage","fromName":"Julian Phillips","fromEmail":"julian@quantumfyre.co.uk","sentAt":"2008-05-08T00:16:26Z","receivedAt":"2008-05-08T00:16:26Z","isPatch":false,"sender":{"key":"julian@quantumfyre.co.uk","avatar":"https://avatars.githubusercontent.com/u/948888?v=4"},"body":"On Wed, 7 May 2008, Daniel Quinlan wrote:\n\n> I'm looking for a way to embed some identifying information about \n> version\n> into compiled programs. I hasten to add that I am not looking to \n> expand RCS-like\n> tags. Unlike CVS/RCS, git provides a single value that characterizes \n> the whole\n> distribution, at least if everything is committed. So, something like \n> \"git log | head -1 | awk '{print $2}'\"\n> probably provides a value which I can embed into executables and \n> libraries, tying\n> them to a particular source configuration. I'm just curious if \n> there's a better approach\n> to getting the commit hash.\n\nsomething like \"git show-ref -s HEAD\" perhaps?\n\n-- \nJulian\n\n ---\nThe Kennedy Constant:\n \tDon't get mad -- get even.\n"},{"id":"76397","messageId":"48235C02.9010808@dirk.my1.cc","threadId":"13320","inReplyTo":"200805072242.m47Mg1o0015578@rs40.luxsci.com","subject":"Re: help with git usage","fromName":"Dirk Süsserott","fromEmail":"newsletter@dirk.my1.cc","sentAt":"2008-05-08T20:01:06Z","receivedAt":"2008-05-08T20:01:06Z","isPatch":false,"sender":{"key":"newsletter@dirk.my1.cc","avatar":null},"body":"Hi,\n\nwhat about using git-describe? At work we use sth. similar to the\nfollowing script. Let's call it 'git-stamp':\n\n-------------\n#!/usr/bin/bash\n\nif [ \"$(git rev-parse --is-inside-work-tree 2>/dev/null)\" = \"true\" ]; then\n here=$(pwd)\n topdir=$(git rev-parse --show-cdup)\n cd ${topdir:-'./'}\n desc=$(git describe)\n if [ $(git diff-index --name-only HEAD | wc -l) -ne 0 ]; then\n desc=\"$desc-dirty\"\n fi\n cd $here\n echo $desc\n exit 0;\nelse\n echo \"Not inside a git working tree.\"\n exit 1;\nfi\n-------------\n\nBasically it outputs the output of 'git-describe'. When something\nwhithin your working dir is currently *not* checked in, it outputs\n\"$(git-describe)-dirty\".\n\nSome sort of \"-D$(git-stamp)\" compiler switch would do the thing.\nDepending on your makefile or scons-script this would yield to a\ncomplete recompile of everything when only one file has changed.\n\nIn our environment we patch $(git-stamp) into some \"version.c\"\nso the whole application only gets recompiled when version.c\nhas changed.\n\nHTH,\n Dirk\n\n\n\nDaniel Quinlan schrieb:\n> Thanks for your earlier responses, they were very helpful.\n>\n> On Apr 30, 2008, at 1:39 AM, Jakub Narebski wrote:\n>\n>> Daniel Barkalow writes:\n>>\n>>> On Tue, 29 Apr 2008, Daniel Quinlan wrote:\n>>>\n>>>> I've been trying to use git for awhile now, (and I've read a lot\n>>>> of documentation, though maybe my comprehension has not been high\n>>>> enough) but there are several operations which I can't figure out:\n>>\n>> Many of answers to your questions can be found on GitFaq,\n>> http://git.or.cz/gitwiki/GitFaq\n>\n> I should have read this earlier. I don't really understand the\n> details, but I get the idea: make the central repository bare.\n>\n>>\n>\n>>>> 3) Similarly, I can't use the little context diffs I can see in\n>>>> git-gui -- I need to see side by side comparisons; I've become\n>>>> accustomed to tkdiff. It seems like git mergetool knows how to do\n>>>> that in some restricted circumstances, but I want to do it outside\n>>>> the context of a merge.\n>>>\n>>> This I don't know, but you can get particular files from particular\n>>> commits output with \"git show :\", and you can likely wire\n>>> something up.\n>>\n>> From the various graphical comparison tools, Meld has supposedly Git\n>> support (http://meld.sourceforge.net/). Supposedly only because I\n>> have not tested this; see\n>> http://git.or.cz/gitwiki/InterfacesFrontendsAndTools#head-00fbd1ac45fe93dac4653cad3639b3df73d8657e \n>>\n>>\n>\n> I found no mention of git on the meld man page or in the meld mailing \n> list.\n>\n> Here's a (perhaps naive) perl script which uses \"git show\" and wraps \n> around\n> the original tkdiff. Other cvs users might find it useful, though it \n> can surely\n> be improved.\n>\n>\n>\n>\n>\n> I'm looking for a way to embed some identifying information about version\n> into compiled programs. I hasten to add that I am not looking to \n> expand RCS-like\n> tags. Unlike CVS/RCS, git provides a single value that characterizes \n> the whole\n> distribution, at least if everything is committed. So, something like \n> \"git log | head -1 | awk '{print $2}'\"\n> probably provides a value which I can embed into executables and \n> libraries, tying\n> them to a particular source configuration. I'm just curious if \n> there's a better approach\n> to getting the commit hash.\n>\n> -- danq\n>\n>\n"},{"id":"76419","messageId":"200805090107.11838.jnareb@gmail.com","threadId":"13320","inReplyTo":"200805072242.m47Mg1o0015578@rs40.luxsci.com","subject":"Re: help with git usage","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2008-05-08T23:07:10Z","receivedAt":"2008-05-08T23:07:10Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Dnia czwartek 8. maja 2008 00:41, Daniel Quinlan napisał:\n\n> I'm looking for a way to embed some identifying information about  \n> version into compiled programs.  I hasten to add that I am not looking\n> to expand RCS-like tags.  Unlike CVS/RCS, git provides a single value\n> that characterizes the whole distribution, at least if everything is\n> committed. \n\nTake a look how git, tig and Linux kernel does it with *VERSION* file \nand Makefile (you can take a look at Makefile and GIT-VERSION-GEN via \ngitweb web interface, e.g. at http://git.kernel.org or \nhttp://repo.or.cz).\n\nIn short: use git-describe output.\n-- \nJakub Narebski\nPoland\n"}]}