From: Thomas Neumann <tneumann@users.sourceforge.net>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: wishlist: git info
Date: Mon, 12 Nov 2007 23:50:18 +0100 [thread overview]
Message-ID: <4738D8AA.1030604@users.sourceforge.net> (raw)
In-Reply-To: <20071112222106.GE2918@steel.home>
> you're better of just running "gitk --all" at this point. It'll show
> remote branches (with the names of remote repos prepended) and their
> relations to the local repo.
hm, this is not what I am after. I do not want to inspect the history, I
want to see where this repository "belongs" to. Gitk shows me the name
(which is reasonable, of course), but not the URL. And it is a GUI
application, which is not so perfect.
>> 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.
>
> Like what? None of the commands you suggested even touch it.
probably "current working directory" was not the best way to phrase it.
I mean state of the repository, which in my case is a clone of a central
repository.
My commands show (ignoring formatting): 1. the remote repositories with
URL 2. the current head commit hash 3. the date of the head commit.
Which gives a pretty decent idea about the state of the repository.
> Would
>
> git remote -r -v && git log --max-count=1 --pretty=format:'%h %s'
>
> do what you think is what you need?
perhaps, the first command gives me an error (git 1.5.2.5). This here is
nearly ok
git remote && git log --max-count=1 --pretty=format:'%H %cD'
except the missing URL from git remote (but perhaps your options include
it with a newer git version, will test).
> May I suggest you to consider just running "git fetch -v"?
this is has side effects, and is quite slow. Your command sequence above
is more handy (and faster).
So I can emulate git info with an alias, and this is good enough for mew
now, thanks for the hints. Perhaps a somewhat more elaborate version of
git info might be useful for others, too, but this is not urgent.
Thomas
next prev parent reply other threads:[~2007-11-12 23:24 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 [this message]
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=4738D8AA.1030604@users.sourceforge.net \
--to=tneumann@users.sourceforge.net \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
/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).