From: Thomas Neumann <tneumann@users.sourceforge.net>
To: git@vger.kernel.org
Subject: wishlist: git info
Date: Mon, 12 Nov 2007 21:30:56 +0100 [thread overview]
Message-ID: <fhad5q$iia$1@ger.gmane.org> (raw)
Hi,
while git is pleasant to use in everyday work, there is one svn feature
which is miss dearly, namely "svn info". svn info can give information
about specific file objects, but I think its main feature is to use it
without any path and thus just describe the current project.
I use this a lot to quickly find out to which remote repository the
current directory belongs (yes, some work projects tend to look very
similar...) and what is the current state of the directory.
As a crude approximation, "git info" should print something like:
cat .git/config | grep url
git show | head -3
Probably not the most intelligent way to compute it, but you get the
idea. git info should give a brief overview over the current working
directory.
If there is consensus that this is a useful feature I can try to suggest
a patch (although honestly I would prefer that someone else does it, I
am not familiar with the git internals).
Thomas
next reply other threads:[~2007-11-12 20:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 20:30 Thomas Neumann [this message]
2007-11-12 22:21 ` wishlist: git info 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
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='fhad5q$iia$1@ger.gmane.org' \
--to=tneumann@users.sourceforge.net \
--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).