Perhaps also project description (if it exists?)
--

Jakub Narebski

Warsaw, Poland

ShadeHawk on #git
-

> Perhaps also project description (if it exists?)

one can specify a project description? I did not even know this. But

yes, this would be useful, too.

In general I think git info should show everything to quickly understand

what is currently checked out. The name of the current branch should

probably be included, too.

I use an alias with the commands proposed by Alex Riessen for now, but a

more general command would be nice.
Thomas
-

Hi,
Is slightly troubles me that you put so much emphasis on what I would call

"remote information".  I understand that in svn, your working directory 
FWIW I think a much better idea is to have that bash prompt that was

posted some months ago; there's not even a need to run a program manually 
His name is "Riesen", just like in the German translation of the famous

Newton statement.
Ciao,

Dscho
-

now I am misspelled. How should I feel?...
-

Better than if you'd done it yourself in a patch that was allowed to endure

for more than 10000 commits ;-)
--

Andreas Ericsson                   andreas.ericsson@op5.se

OP5 AB                             www.op5.se

Tel: +46 8-230225                  Fax: +46 8-230231

-

I mildly disagree.
Exactly because you can do so much more in isolation than with

other systems like SVN, I tend to think that you would want to

know what "git remote show" gives you, and a lot more (e.g. what

"git shortlog origin@{1}..origin" would give you if you were to

fetch now).  You can deviate from the others quite a lot without

synchronizing, because git allows you to do so very easily, and

I can understand that some people will find it scary when it

comes to the point to synchronize with the others.
A stronger support to learn "what happened there while I was

looking the other way" would be a definite plus.
But "project description"?  Give me a break.  If you have cloned

the repository (or learned the existence of repository), you

already learned from elsewhere what the project is about.
I haven't spoken in this thread because honestly I found most of

the things mentioned here were totally uninteresting.

-

well, not that I asked for the project description, but I see a small

benefit there. The point is not to know what the project is about. You

know, after all you checked it out in the first place. My goal is to

quickly/easily see "what is in this directory".
Perhaps my usage pattern is obscure, but I have something like 40

repositories checked out in different directories, and I sometimes loose

track of what actually is in a certain directory (and in what state). A

simple "ls" is not enough, as some of them look very similar on the top

sorry for this. While I find it useful, this is certainly not an

important feature, and I can mimic it now myself.
Thomas

-

Don't get me wrong.  My not finding it useful does not mean it

won't be useful in the git user comminity in general.  It just

means I do not have a useful input to the discussion.

-

I had that problem too, until I realized that what I really needed was to

clone repos out with the same careful structure we're using on the server,

and then just use \w instead of \W in my $PS1.
--

Andreas Ericsson                   andreas.ericsson@op5.se

OP5 AB                             www.op5.se

Tel: +46 8-230225                  Fax: +46 8-230231

-

that is true. My usage pattern probably stems from the fact that I am a

long term svn user :) And I use git for work now, where there is indeed

some kind of central repository just as in a Subversion setting.

In a fully decentralized setting the remote information is probably not

as important, although you might still want to know what happens if you

a bash prompt is nice too, of course. But there is only so much

information you can reasonably encode in the prompt.

When you know the remote url (ok, this assumes a "centralized" model),

branch, head commit and date of the head commit (this is just for

humans), you know very precisely what you are looking at. For the more

decentralized users some other information might be relevant, I don't know.
While the head commit hash is enough to identify a point in the revision

history, the other information allows a human to identify the point in

the revision history easily. So I can see what is checked out, how old

sorry for the typo, I noticed it just the moment I had pressed send...

Sometimes I really wish I could edit mails after sending them.
Thomas

-

The remote URL isn't /the/ useful bit, most of the time. Either you have ju=

st

one remote, which is the project central repository and you probably know

which it is just by knowing which project it is, or you have many of them a=

nd

their names tell you enough.
Note, that unlike in Subversion, the branch name is /not/ part of the URL.

And that is the useful bit of the information. So what 'git info' probably

should show is:

 - Which branch is currently checked out

 - Which branch it is tracking (inspect the config)

 - List of n (where n is small integer) "closest" branches, where the

   distance to a branch is number of commits in HEAD since common ancestor

   with that branch.

 - Latest included tag. Basically something like git describe.

 - Short log of last few commits.
--=20

						 Jan 'Bulb' Hudec <bulb@ucw.cz>