All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Lehmann <Jens.Lehmann@web.de>
To: Sergio Callegari <sergio.callegari@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Possible bug with git status in 1.7.0
Date: Fri, 19 Feb 2010 21:55:52 +0100	[thread overview]
Message-ID: <4B7EFAD8.9040309@web.de> (raw)
In-Reply-To: <4B7EBF7B.3090703@gmail.com>

Am 19.02.2010 17:42, schrieb Sergio Callegari:
> Yes! My ideal behavior (if I am not asking too much) would be trying to
> keep the status as little wordy as possible (1 line per submodule)
> 
> e.g. something like
> 
> #       modified module (commit id):   mod1
> #       modified module (modified files): mod2
> #    modified module (untracked files): mod3
> #       modified module (modified files, untracked files): mod4
> #    modified module (commit id, modified files, untracked files): mod5

Yup, one line per submodule should be enough. But maybe it's nicer to
have the details /after/ the submodule name:

#	modified:   mod1 (Submodule has new commit(s), modified content, untracked content)

Then it fits more nicely with the output for files, no?

We could drop the "Submodule has " if people see it as a waste of screen
estate. Also i have no strong feelings about "content", i just happen to
think it is more appropriate as submodules can contain not only files but
other submodules too. Opinions?

Will send a patch for discussion as soon as i have something to show ...

  reply	other threads:[~2010-02-19 20:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 19:14 Possible bug with git status in 1.7.0 Sergio
2010-02-17 19:21 ` Junio C Hamano
2010-02-17 19:52   ` Sergio Callegari
2010-02-17 20:52     ` Jens Lehmann
2010-02-19 16:42       ` Sergio Callegari
2010-02-19 20:55         ` Jens Lehmann [this message]
2010-02-20 11:05           ` Sergio Callegari

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=4B7EFAD8.9040309@web.de \
    --to=jens.lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=sergio.callegari@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.