git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergio Callegari <sergio.callegari@gmail.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Possible bug with git status in 1.7.0
Date: Sat, 20 Feb 2010 12:05:02 +0100	[thread overview]
Message-ID: <4B7FC1DE.2020802@gmail.com> (raw)
In-Reply-To: <4B7EFAD8.9040309@web.de>

Jens Lehmann wrote:
> 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 ...
>   
How about

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

trying to assure that what comes after the ":" is a list of comma 
separated properties.

This can make the thing easier to parse.  I know that there is a "git 
status ---porcelain" but from my understanding it will not be possible 
to get this kind of information from that command since its output 
format is frozen and not extensible, so many could resort to try to 
parse the "normal" git status output to get all the info about 
submodules at once.

Even better would be to have a "--interface_level 2" to go with 
---porcelain, to be able to pass this info even there.

BTW... about the --porcelain option, I wonder if considering an alias to 
--parseable could be on the list.  The plumbing/porcelain metaphor is 
really nice, but a --porcelain option can probably be a bit confusing 
for the beginner getting a

usage: git status [options] [--] <filepattern>...

    -v, --verbose         be verbose
    -s, --short           show status concisely
    --porcelain           show porcelain output format
    -z, --null            terminate entries with NUL
    -u, --untracked-files[=<mode>]
                          show untracked files, optional modes: all, 
normal, no. (Default: all)

considering that status is probably the first command the beginner may 
come into.

Sergio

      reply	other threads:[~2010-02-20 11:05 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
2010-02-20 11:05           ` Sergio Callegari [this message]

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=4B7FC1DE.2020802@gmail.com \
    --to=sergio.callegari@gmail.com \
    --cc=Jens.Lehmann@web.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).