{"thread":{"id":"10836","subject":"wishlist: git info","startedAt":"2007-11-12T20:30:56Z","lastAt":"2007-11-17T16:21:01Z","messageCount":17,"participants":["Thomas Neumann","Alex Riesen","Jakub Narebski","Johannes Schindelin","Junio C Hamano","Andreas Ericsson","Jan Hudec"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"59567","messageId":"fhad5q$iia$1@ger.gmane.org","threadId":"10836","inReplyTo":null,"subject":"wishlist: git info","fromName":"Thomas Neumann","fromEmail":"tneumann@users.sourceforge.net","sentAt":"2007-11-12T20:30:56Z","receivedAt":"2007-11-12T20:30:56Z","isPatch":false,"sender":{"key":"tneumann@users.sourceforge.net","avatar":null},"body":"Hi,\n\nwhile git is pleasant to use in everyday work, there is one svn feature\nwhich is miss dearly, namely \"svn info\". svn info can give information\nabout specific file objects, but I think its main feature is to use it\nwithout any path and thus just describe the current project.\nI use this a lot to quickly find out to which remote repository the\ncurrent directory belongs (yes, some work projects tend to look very\nsimilar...) and what is the current state of the directory.\n\nAs a crude approximation, \"git info\" should print something like:\ncat .git/config | grep url\ngit show | head -3\n\nProbably not the most intelligent way to compute it, but you get the\nidea. git info should give a brief overview over the current working\ndirectory.\nIf there is consensus that this is a useful feature I can try to suggest\na patch (although honestly I would prefer that someone else does it, I\nam not familiar with the git internals).\n\nThomas\n"},{"id":"59586","messageId":"20071112222106.GE2918@steel.home","threadId":"10836","inReplyTo":"fhad5q$iia$1@ger.gmane.org","subject":"Re: wishlist: git info","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2007-11-12T22:21:06Z","receivedAt":"2007-11-12T22:21:06Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"Thomas Neumann, Mon, Nov 12, 2007 21:30:56 +0100:\n> while git is pleasant to use in everyday work, there is one svn feature\n> which is miss dearly, namely \"svn info\". svn info can give information\n> about specific file objects, but I think its main feature is to use it\n> without any path and thus just describe the current project.\n> I use this a lot to quickly find out to which remote repository the\n> current directory belongs (yes, some work projects tend to look very\n> similar...) and what is the current state of the directory.\n> \n> As a crude approximation, \"git info\" should print something like:\n> cat .git/config | grep url\n> git show | head -3\n\nyou're better of just running \"gitk --all\" at this point. It'll show\nremote branches (with the names of remote repos prepended) and their\nrelations to the local repo.\n\n> Probably not the most intelligent way to compute it, but you get the\n> idea. git info should give a brief overview over the current working\n> directory.\n\nLike what? None of the commands you suggested even touch it.\nWould\n\n git remote -r -v && git log --max-count=1 --pretty=format:'%h %s'\n\ndo what you think is what you need?\n\nMay I suggest you to consider just running \"git fetch -v\"?\n"},{"id":"59595","messageId":"4738D8AA.1030604@users.sourceforge.net","threadId":"10836","inReplyTo":"20071112222106.GE2918@steel.home","subject":"Re: wishlist: git info","fromName":"Thomas Neumann","fromEmail":"tneumann@users.sourceforge.net","sentAt":"2007-11-12T22:50:18Z","receivedAt":"2007-11-12T22:50:18Z","isPatch":false,"sender":{"key":"tneumann@users.sourceforge.net","avatar":null},"body":"> you're better of just running \"gitk --all\" at this point. It'll show\n> remote branches (with the names of remote repos prepended) and their\n> relations to the local repo.\nhm, this is not what I am after. I do not want to inspect the history, I\nwant to see where this repository \"belongs\" to. Gitk shows me the name\n(which is reasonable, of course), but not the URL. And it is a GUI\napplication, which is not so perfect.\n\n>> Probably not the most intelligent way to compute it, but you get the\n>> idea. git info should give a brief overview over the current working\n>> directory.\n>\n> Like what? None of the commands you suggested even touch it.\nprobably \"current working directory\" was not the best way to phrase it.\nI mean state of the repository, which in my case is a clone of a central\nrepository.\nMy commands show (ignoring formatting): 1. the remote repositories with\nURL 2. the current head commit hash 3. the date of the head commit.\nWhich gives a pretty decent idea about the state of the repository.\n\n> Would\n>\n> git remote -r -v && git log --max-count=1 --pretty=format:'%h %s'\n>\n> do what you think is what you need?\nperhaps, the first command gives me an error (git 1.5.2.5). This here is\nnearly ok\n\ngit remote && git log --max-count=1 --pretty=format:'%H %cD'\n\nexcept the missing URL from git remote (but perhaps your options include\nit with a newer git version, will test).\n\n> May I suggest you to consider just running \"git fetch -v\"?\nthis is has side effects, and is quite slow. Your command sequence above\n is more handy (and faster).\n\nSo I can emulate git info with an alias, and this is good enough for mew\nnow, thanks for the hints. Perhaps a somewhat more elaborate version of\ngit info might be useful for others, too, but this is not urgent.\n\nThomas\n"},{"id":"59598","messageId":"20071112234115.GJ2918@steel.home","threadId":"10836","inReplyTo":"4738D8AA.1030604@users.sourceforge.net","subject":"Re: wishlist: git info","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2007-11-12T23:41:15Z","receivedAt":"2007-11-12T23:41:15Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"Thomas Neumann, Mon, Nov 12, 2007 23:50:18 +0100:\n> >> Probably not the most intelligent way to compute it, but you get the\n> >> idea. git info should give a brief overview over the current working\n> >> directory.\n> >\n> > Like what? None of the commands you suggested even touch it.\n> probably \"current working directory\" was not the best way to phrase it.\n> I mean state of the repository, which in my case is a clone of a central\n> repository.\n> My commands show (ignoring formatting): 1. the remote repositories with\n> URL 2. the current head commit hash 3. the date of the head commit.\n\nDon't you want to know where the remote repo is at?\n\n> Which gives a pretty decent idea about the state of the repository.\n\n...which in Git-lingo would be misunderstood as the output of\ngit-status :)\n\n> > Would\n> >\n> > git remote -r -v && git log --max-count=1 --pretty=format:'%h %s'\n> >\n> > do what you think is what you need?\n> perhaps, the first command gives me an error (git 1.5.2.5). This here is\n> nearly ok\n\nAch, make it \"git remote -v\". It does exactly showing of the url.\n\nDunno what I wanted the \"-r\" for. Probably left from thinking of\n\"git branch -r\" (which shows remote branches).\n\n> git remote && git log --max-count=1 --pretty=format:'%H %cD'\n> \n> except the missing URL from git remote (but perhaps your options include\n> it with a newer git version, will test).\n\nIt is there since 1.5.3-rc1\n"},{"id":"59599","messageId":"fhaol0$p5r$1@ger.gmane.org","threadId":"10836","inReplyTo":"4738D8AA.1030604@users.sourceforge.net","subject":"Re: wishlist: git info","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2007-11-12T23:46:37Z","receivedAt":"2007-11-12T23:46:37Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Thomas Neumann wrote:\n\n> My commands show (ignoring formatting): 1. the remote repositories with\n> URL 2. the current head commit hash 3. the date of the head commit.\n> Which gives a pretty decent idea about the state of the repository.\n\nPerhaps also project description (if it exists?)\n\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"},{"id":"59633","messageId":"fhbn50$uqu$1@ger.gmane.org","threadId":"10836","inReplyTo":"fhaol0$p5r$1@ger.gmane.org","subject":"Re: wishlist: git info","fromName":"Thomas Neumann","fromEmail":"tneumann@users.sourceforge.net","sentAt":"2007-11-13T08:27:20Z","receivedAt":"2007-11-13T08:27:20Z","isPatch":false,"sender":{"key":"tneumann@users.sourceforge.net","avatar":null},"body":"> Perhaps also project description (if it exists?)\none can specify a project description? I did not even know this. But\nyes, this would be useful, too.\nIn general I think git info should show everything to quickly understand\nwhat is currently checked out. The name of the current branch should\nprobably be included, too.\nI use an alias with the commands proposed by Alex Riessen for now, but a\nmore general command would be nice.\n\nThomas\n"},{"id":"59638","messageId":"fhbrll$ceq$1@ger.gmane.org","threadId":"10836","inReplyTo":"fhbn50$uqu$1@ger.gmane.org","subject":"Re: wishlist: git info","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2007-11-13T09:44:25Z","receivedAt":"2007-11-13T09:44:25Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Thomas Neumann wrote:\n\n>> Perhaps also project description (if it exists?)\n\n> one can specify a project description? I did not even know this. But\n> yes, this would be useful, too.\n\nIt is project description for gitweb (git web interface), and I think also\nfor other web interfaces (cgit, wit, git-php). Or rather *repository*\ndescription. It is in .git/description (in 'description' file in git\nrepository).\n\nUnfortunately by default it contains (see: ${tempate_dir}/description)\n\n Unnamed repository; edit this file to name it for gitweb.\n\n> In general I think git info should show everything to quickly understand\n> what is currently checked out. The name of the current branch should\n> probably be included, too.\n\nName of current branch, current directory, name of topdir (with '.git'\nstripped if it is bare repository), perhaps oneline description of top\ncommit. And if branch is under StGit or Guilt (patch management interfaces)\ncontrol.\n\nSee also helper functions to set shell prompt in\ncontrib/completion/git-completion.bash. \n\nI for example have \"1760:[gitweb/web!git]$ \" as bash prompt:\n - 1760 is number of command in history, \n - 'gitweb/web' is name of branch I am on,\n - 'git' is the name of repository\nThis migitates need got 'git-info' command.\n\n> I use an alias with the commands proposed by Alex Riessen for now, but a\n> more general command would be nice.\n\nYou can always write[*1*] git-info.sh or git-info.perl[*2*], and install it\nas git-info in your git installation. And send patches here, to git mailing\nlist, for comments.\n\nFootnotes:\n----------\n[*1*] Even if one of the most common complaints is \"too many user-visible\n commands\".\n[*2*] Scripts are better for ptototyping. Choose your own poison: POSIX\n shell or Perl...\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"},{"id":"59653","messageId":"Pine.LNX.4.64.0711131111220.4362@racer.site","threadId":"10836","inReplyTo":"fhbn50$uqu$1@ger.gmane.org","subject":"Re: wishlist: git info","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2007-11-13T11:13:59Z","receivedAt":"2007-11-13T11:13:59Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Tue, 13 Nov 2007, Thomas Neumann wrote:\n\n> Perhaps also project description (if it exists?) one can specify a \n> project description? I did not even know this. But yes, this would be \n> useful, too. In general I think git info should show everything to \n> quickly understand what is currently checked out.\n\nIs slightly troubles me that you put so much emphasis on what I would call \n\"remote information\". I understand that in svn, your working directory \nwithout the server is not very useful. But we do not have that problem.\n\n> The name of the current branch should probably be included, too.\n\nFWIW I think a much better idea is to have that bash prompt that was \nposted some months ago; there's not even a need to run a program manually \nthen!\n\n> I use an alias with the commands proposed by Alex Riessen for now, but a \n> more general command would be nice.\n\nHis name is \"Riesen\", just like in the German translation of the famous \nNewton statement.\n\nCiao,\nDscho\n"},{"id":"59655","messageId":"47398B43.30408@users.sourceforge.net","threadId":"10836","inReplyTo":"Pine.LNX.4.64.0711131111220.4362@racer.site","subject":"Re: wishlist: git info","fromName":"Thomas Neumann","fromEmail":"tneumann@users.sourceforge.net","sentAt":"2007-11-13T11:32:19Z","receivedAt":"2007-11-13T11:32:19Z","isPatch":false,"sender":{"key":"tneumann@users.sourceforge.net","avatar":null},"body":"> Is slightly troubles me that you put so much emphasis on what I would call \n> \"remote information\". I understand that in svn, your working directory \n> without the server is not very useful. But we do not have that problem.\nthat is true. My usage pattern probably stems from the fact that I am a\nlong term svn user :) And I use git for work now, where there is indeed\nsome kind of central repository just as in a Subversion setting.\nIn a fully decentralized setting the remote information is probably not\nas important, although you might still want to know what happens if you\nissue \"git pull\".\n\n\n> FWIW I think a much better idea is to have that bash prompt that was \n> posted some months ago; there's not even a need to run a program manually \n> then!\na bash prompt is nice too, of course. But there is only so much\ninformation you can reasonably encode in the prompt.\nWhen you know the remote url (ok, this assumes a \"centralized\" model),\nbranch, head commit and date of the head commit (this is just for\nhumans), you know very precisely what you are looking at. For the more\ndecentralized users some other information might be relevant, I don't know.\n\nWhile the head commit hash is enough to identify a point in the revision\nhistory, the other information allows a human to identify the point in\nthe revision history easily. So I can see what is checked out, how old\nthe checkout is etc.\n\n> His name is \"Riesen\", just like in the German translation of the famous \n> Newton statement.\nsorry for the typo, I noticed it just the moment I had pressed send...\nSometimes I really wish I could edit mails after sending them.\n\nThomas\n"},{"id":"59665","messageId":"fhcbrr$ef$3@ger.gmane.org","threadId":"10836","inReplyTo":"fhbrll$ceq$1@ger.gmane.org","subject":"Re: wishlist: git info","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2007-11-13T14:20:44Z","receivedAt":"2007-11-13T14:20:44Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Jakub Narebski wrote:\n> Thomas Neumann wrote:\n\n> You can always write[*1*] git-info.sh or git-info.perl, and install\n> it as git-info in your git installation. And send patches here, to git\n> mailing list, for comments.\n> \n> Footnotes:\n> ----------\n> [*1*] Even if one of the most common complaints is \"too many user-visible\n> commands\".\n\nOn the other hand one of the proposed and long requested features is\ngit-explain, which is meant to show status of git command progress. If you\ncould incorporate proposed features in git-info (perhaps only with some\noption: --state, --explain, -v / --verbose,...) there would be no\ncomplaints about yet another git command.\n\nWhat git-info / git-explain should show:\n * interrupted fetch / fetch in progress\n * interrupted pull / pull in progress\n * interrupted merge / merge in progress\n * interrupted commit, commit --amend, or tag editing\n * rebase in progress (including interactive rebase and rebasing\n using merge engine)\n * git-am (apply mbox) in progress\n\nPerhaps we should also include git-count-objects in git-info, like\ngit-verify-tag functionality was included in 'git tag --verify'...\n\n-- \nJakub Narebski\nWarsaw, Poland\nShadeHawk on #git\n"},{"id":"59694","messageId":"7v3avat147.fsf@gitster.siamese.dyndns.org","threadId":"10836","inReplyTo":"Pine.LNX.4.64.0711131111220.4362@racer.site","subject":"Re: wishlist: git info","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-11-13T19:08:08Z","receivedAt":"2007-11-13T19:08:08Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Johannes Schindelin writes:\n\n> On Tue, 13 Nov 2007, Thomas Neumann wrote:\n>\n>> Perhaps also project description (if it exists?) one can specify a \n>> project description? I did not even know this. But yes, this would be \n>> useful, too. In general I think git info should show everything to \n>> quickly understand what is currently checked out.\n>\n> Is slightly troubles me that you put so much emphasis on what I would call \n> \"remote information\". I understand that in svn, your working directory \n> without the server is not very useful. But we do not have that problem.\n\nI mildly disagree.\n\nExactly because you can do so much more in isolation than with\nother systems like SVN, I tend to think that you would want to\nknow what \"git remote show\" gives you, and a lot more (e.g. what\n\"git shortlog origin@{1}..origin\" would give you if you were to\nfetch now). You can deviate from the others quite a lot without\nsynchronizing, because git allows you to do so very easily, and\nI can understand that some people will find it scary when it\ncomes to the point to synchronize with the others.\n\nA stronger support to learn \"what happened there while I was\nlooking the other way\" would be a definite plus.\n\nBut \"project description\"? Give me a break. If you have cloned\nthe repository (or learned the existence of repository), you\nalready learned from elsewhere what the project is about.\n\nI haven't spoken in this thread because honestly I found most of\nthe things mentioned here were totally uninteresting.\n"},{"id":"59699","messageId":"4739F9F7.20407@users.sourceforge.net","threadId":"10836","inReplyTo":"7v3avat147.fsf@gitster.siamese.dyndns.org","subject":"Re: wishlist: git info","fromName":"Thomas Neumann","fromEmail":"tneumann@users.sourceforge.net","sentAt":"2007-11-13T19:24:39Z","receivedAt":"2007-11-13T19:24:39Z","isPatch":false,"sender":{"key":"tneumann@users.sourceforge.net","avatar":null},"body":"> But \"project description\"? Give me a break. If you have cloned\n> the repository (or learned the existence of repository), you\n> already learned from elsewhere what the project is about.\nwell, not that I asked for the project description, but I see a small\nbenefit there. The point is not to know what the project is about. You\nknow, after all you checked it out in the first place. My goal is to\nquickly/easily see \"what is in this directory\".\n\nPerhaps my usage pattern is obscure, but I have something like 40\nrepositories checked out in different directories, and I sometimes loose\ntrack of what actually is in a certain directory (and in what state). A\nsimple \"ls\" is not enough, as some of them look very similar on the top\nlevel. Hence my interest for \"git info\".\n\n> I haven't spoken in this thread because honestly I found most of\n> the things mentioned here were totally uninteresting.\nsorry for this. While I find it useful, this is certainly not an\nimportant feature, and I can mimic it now myself.\n\nThomas\n"},{"id":"59705","messageId":"4739FFDA.8020702@op5.se","threadId":"10836","inReplyTo":"4739F9F7.20407@users.sourceforge.net","subject":"Re: wishlist: git info","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2007-11-13T19:49:46Z","receivedAt":"2007-11-13T19:49:46Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"Thomas Neumann wrote:\n>> But \"project description\"? Give me a break. If you have cloned\n>> the repository (or learned the existence of repository), you\n>> already learned from elsewhere what the project is about.\n> well, not that I asked for the project description, but I see a small\n> benefit there. The point is not to know what the project is about. You\n> know, after all you checked it out in the first place. My goal is to\n> quickly/easily see \"what is in this directory\".\n> \n> Perhaps my usage pattern is obscure, but I have something like 40\n> repositories checked out in different directories, and I sometimes loose\n> track of what actually is in a certain directory (and in what state). A\n> simple \"ls\" is not enough, as some of them look very similar on the top\n> level. Hence my interest for \"git info\".\n> \n\nI had that problem too, until I realized that what I really needed was to\nclone repos out with the same careful structure we're using on the server,\nand then just use \\w instead of \\W in my $PS1.\n\n-- \nAndreas Ericsson andreas.ericsson@op5.se\nOP5 AB www.op5.se\nTel: +46 8-230225 Fax: +46 8-230231\n"},{"id":"59723","messageId":"7vprydsyfm.fsf@gitster.siamese.dyndns.org","threadId":"10836","inReplyTo":"4739F9F7.20407@users.sourceforge.net","subject":"Re: wishlist: git info","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-11-13T20:06:05Z","receivedAt":"2007-11-13T20:06:05Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Thomas Neumann writes:\n\n>> I haven't spoken in this thread because honestly I found most of\n>> the things mentioned here were totally uninteresting.\n>\n> sorry for this. While I find it useful, this is certainly not an\n> important feature, and I can mimic it now myself.\n\nDon't get me wrong. My not finding it useful does not mean it\nwon't be useful in the git user comminity in general. It just\nmeans I do not have a useful input to the discussion.\n"},{"id":"59735","messageId":"20071113212259.GG3268@steel.home","threadId":"10836","inReplyTo":"Pine.LNX.4.64.0711131111220.4362@racer.site","subject":"Re: wishlist: git info","fromName":"Alex Riesen","fromEmail":"raa.lkml@gmail.com","sentAt":"2007-11-13T21:22:59Z","receivedAt":"2007-11-13T21:22:59Z","isPatch":false,"sender":{"key":"raa.lkml@gmail.com","avatar":"https://avatars.githubusercontent.com/u/324101?v=4"},"body":"Johannes Schindelin, Tue, Nov 13, 2007 12:13:59 +0100:\n> > I use an alias with the commands proposed by Alex Riessen for now, but a \n> > more general command would be nice.\n> \n> His name is \"Riesen\", just like in the German translation of the famous \n> Newton statement.\n\nnow I am misspelled. How should I feel?...\n"},{"id":"59759","messageId":"473A23C8.5020904@op5.se","threadId":"10836","inReplyTo":"20071113212259.GG3268@steel.home","subject":"Re: wishlist: git info","fromName":"Andreas Ericsson","fromEmail":"ae@op5.se","sentAt":"2007-11-13T22:23:04Z","receivedAt":"2007-11-13T22:23:04Z","isPatch":false,"sender":{"key":"ae@op5.se","avatar":"https://gravatar.com/avatar/426e89595c75a8f5252dd0c989e5fabe5bcac616e68557427ad9aef6b0ca342a?d=mp&s=160"},"body":"Alex Riesen wrote:\n> Johannes Schindelin, Tue, Nov 13, 2007 12:13:59 +0100:\n>>> I use an alias with the commands proposed by Alex Riessen for now, but a \n>>> more general command would be nice.\n>> His name is \"Riesen\", just like in the German translation of the famous \n>> Newton statement.\n> \n> now I am misspelled. How should I feel?...\n> \n\nBetter than if you'd done it yourself in a patch that was allowed to endure\nfor more than 10000 commits ;-)\n\n-- \nAndreas Ericsson andreas.ericsson@op5.se\nOP5 AB www.op5.se\nTel: +46 8-230225 Fax: +46 8-230231\n"},{"id":"60149","messageId":"20071117162101.GA5198@efreet.light.src","threadId":"10836","inReplyTo":"47398B43.30408@users.sourceforge.net","subject":"Re: wishlist: git info","fromName":"Jan Hudec","fromEmail":"bulb@ucw.cz","sentAt":"2007-11-17T16:21:01Z","receivedAt":"2007-11-17T16:21:01Z","isPatch":false,"sender":{"key":"bulb@ucw.cz","avatar":null},"body":"On Tue, Nov 13, 2007 at 12:32:19 +0100, Thomas Neumann wrote:\n> > Is slightly troubles me that you put so much emphasis on what I would call \n> > \"remote information\". I understand that in svn, your working directory \n> > without the server is not very useful. But we do not have that problem.\n> that is true. My usage pattern probably stems from the fact that I am a\n> long term svn user :) And I use git for work now, where there is indeed\n> some kind of central repository just as in a Subversion setting.\n> In a fully decentralized setting the remote information is probably not\n> as important, although you might still want to know what happens if you\n> issue \"git pull\".\n\nThe remote URL isn't /the/ useful bit, most of the time. Either you have just\none remote, which is the project central repository and you probably know\nwhich it is just by knowing which project it is, or you have many of them and\ntheir names tell you enough.\n\nNote, that unlike in Subversion, the branch name is /not/ part of the URL.\nAnd that is the useful bit of the information. So what 'git info' probably\nshould show is:\n - Which branch is currently checked out\n - Which branch it is tracking (inspect the config)\n - List of n (where n is small integer) \"closest\" branches, where the\n distance to a branch is number of commits in HEAD since common ancestor\n with that branch.\n - Latest included tag. Basically something like git describe.\n - Short log of last few commits.\n\n-- \n\t\t\t\t\t\t Jan 'Bulb' Hudec \n"}]}