git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Neumann <tneumann@users.sourceforge.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: wishlist: git info
Date: Tue, 13 Nov 2007 12:32:19 +0100	[thread overview]
Message-ID: <47398B43.30408@users.sourceforge.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0711131111220.4362@racer.site>

> 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 
> without the server is not very useful.  But we do not have that problem.
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
issue "git pull".


> 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 
> then!
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
the checkout is etc.

> His name is "Riesen", just like in the German translation of the famous 
> Newton statement.
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

  reply	other threads:[~2007-11-13 11:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12 20:30 wishlist: git info Thomas Neumann
2007-11-12 22:21 ` Alex Riesen
2007-11-12 22:50   ` Thomas Neumann
2007-11-12 23:41     ` Alex Riesen
2007-11-12 23:46     ` Jakub Narebski
2007-11-13  8:27       ` Thomas Neumann
2007-11-13  9:44         ` Jakub Narebski
2007-11-13 14:20           ` Jakub Narebski
2007-11-13 11:13         ` Johannes Schindelin
2007-11-13 11:32           ` Thomas Neumann [this message]
2007-11-17 16:21             ` Jan Hudec
2007-11-13 19:08           ` Junio C Hamano
2007-11-13 19:24             ` Thomas Neumann
2007-11-13 19:49               ` Andreas Ericsson
2007-11-13 20:06               ` Junio C Hamano
2007-11-13 21:22           ` Alex Riesen
2007-11-13 22:23             ` Andreas Ericsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47398B43.30408@users.sourceforge.net \
    --to=tneumann@users.sourceforge.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).