Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: bill lam <cbill.lam@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: commit --quiet option
Date: Tue, 24 Nov 2009 17:10:35 -0800	[thread overview]
Message-ID: <7vtywj76k4.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 20091124051622.GB18003@debian.b2j

bill lam <cbill.lam@gmail.com> writes:

> In git version 1.6.6.rc0.15.g4fa8a0 using the --quiet option it still
> show some output.  Is that intended?  Specifically I would like to
> exclude message about the untracked files when using --quite option.

Given that you are getting "you told me to make a commit without preparing
anything to commit" error message, I think it can be argued in both ways.

    $ git commit -q -uno -m 'meaningless message'

would omit the listing of Untracked files; a better alternative, depending
on what are listed in the section (I take "a123" is an example made-up for
reproduction recipe, and you are probably getting something like 'foo.bak'
in real life), might be to update your .gitignore, though.

> $ git commit -q -m commit
> # On branch master
> # Changed but not updated:
> #   (use "git add <file>..." to update what will be committed)
> #   (use "git checkout -- <file>..." to discard changes in working directory)
> #
> #       modified:   .git-completion.bash
> #       modified:   bin/mirrorgit
> #
> # Untracked files:
> #   (use "git add <file>..." to include in what will be committed)
> #
> #       a123
> no changes added to commit (use "git add" and/or "git commit -a")
>
> -- 
> regards,
> ====================================================
> GPG key 1024D/4434BAB3 2008-08-24
> gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3

  reply	other threads:[~2009-11-25  1:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24  5:16 commit --quiet option bill lam
2009-11-25  1:10 ` Junio C Hamano [this message]
2009-11-25  2:06   ` bill lam

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=7vtywj76k4.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=cbill.lam@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