From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Thomas Neumann <tneumann@users.sourceforge.net>
Cc: git@vger.kernel.org
Subject: Re: wishlist: git info
Date: Tue, 13 Nov 2007 11:13:59 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711131111220.4362@racer.site> (raw)
In-Reply-To: <fhbn50$uqu$1@ger.gmane.org>
Hi,
On Tue, 13 Nov 2007, Thomas Neumann wrote:
> 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.
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.
> The name of the current branch should probably be included, too.
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!
> I use an alias with the commands proposed by Alex Riessen for now, but a
> more general command would be nice.
His name is "Riesen", just like in the German translation of the famous
Newton statement.
Ciao,
Dscho
next prev parent reply other threads:[~2007-11-13 11:14 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 [this message]
2007-11-13 11:32 ` Thomas Neumann
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=Pine.LNX.4.64.0711131111220.4362@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=tneumann@users.sourceforge.net \
/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).