git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Unknown <borg@uu3.net>
To: David Aguilar <davvid@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git status -q (similar to subversion)
Date: Mon, 29 Jun 2009 21:39:18 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0906292131330.27727@cube> (raw)
In-Reply-To: <20090628224447.GB1951@gmail.com>

On Sun, 28 Jun 2009, David Aguilar wrote:

> Hello
Hi and thanks for reply.

> Please take a look at Documentation/SubmittingPatches
> (all of the documentation lives in Documentation/).
>
> It doesn't seem like this patch was generated with
> git format-patch.  You'll also want to submit your patch using
> git send-email, as we require inline patches instead of
> attachments.
Right. I though such a small patch can be provided as is.
Anyway, I will take necessary steps to peform better next time.

The question is, would that patch will be applied anyway?
I already received some criticism about not applying it.
I can only answer that where svn status and git status differ in many 
cases, there are also similar in some.

For now, I would rather want to see a discus about it (Pro vs Cons).

Other solution I see is add extra config variable like:
status.showUntrackedDefault = (no|normal|all)
So when you peform 'git status -u' it will be used.

Looks better to me if we really want to have difference between
git status vs svn status.

Regards,
Borg

  reply	other threads:[~2009-06-29 19:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-27 20:57 [PATCH] git status -q (similar to subversion) Unknown
2009-06-28 18:52 ` Jeff King
2009-06-28 21:01   ` Martin Renold
2009-06-30  5:33     ` Jeff King
2009-06-30 15:14       ` Martin Renold
2009-06-30 15:33         ` Jeff King
2009-07-01  8:37           ` Paolo Bonzini
2009-06-28 22:44 ` David Aguilar
2009-06-29 19:39   ` Unknown [this message]
2009-06-30  5:33     ` Jeff King
2009-06-30 16:56       ` Unknown

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=Pine.LNX.4.64.0906292131330.27727@cube \
    --to=borg@uu3.net \
    --cc=davvid@gmail.com \
    --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).