git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Thomas Neumann <tneumann@users.sourceforge.net>, git@vger.kernel.org
Subject: Re: wishlist: git info
Date: Tue, 13 Nov 2007 11:08:08 -0800	[thread overview]
Message-ID: <7v3avat147.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0711131111220.4362@racer.site> (Johannes Schindelin's message of "Tue, 13 Nov 2007 11:13:59 +0000 (GMT)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> 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.

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.

  parent reply	other threads:[~2007-11-13 19:13 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
2007-11-17 16:21             ` Jan Hudec
2007-11-13 19:08           ` Junio C Hamano [this message]
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=7v3avat147.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=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).