All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Rossel <rrossel@inf.utfsm.cl>
To: git@vger.kernel.org
Subject: Re: git gc logs to standard error
Date: Mon, 14 Dec 2009 13:37:33 -0300	[thread overview]
Message-ID: <4B2669CD.9020505@inf.utfsm.cl> (raw)
In-Reply-To: <8c9a060912140828p3b05972lf9abc82c7b0f9bc1@mail.gmail.com>

>
> On Mon, Dec 14, 2009 at 08:23, Richard Rossel<rrossel@inf.utfsm.cl>  wrote:
>    
>> $ git --version
>> git version 1.5.4.3
>>
>> And when there is no change in the repo
>>
>> $ git fetch --q; echo $?
>> 0
>>
>> no messages and no error , but when there is a change to syncronize
>>
>> $ git fetch --q; echo $?
>> remote: Counting objects: 7, done.
>> remote: Compressing objects: 100% (5/5), done.
>> remote: Total 5 (delta remote: 2), reused 0 (delta 0)
>> Unpacking objects: 100% (5/5), done.
>>  From git@boss:sandbox
>>    3e4df7f..b92d27c  master     ->  origin/master
>> 0
>>
>>      
> Don't use a double dash, if you're using the short option.
>
> git fetch -q
> OR
> git fetch --quiet
>
> git fetch --q<--- This is not what you think it is.
>
> -Jacob
>
>    
doh, sorry, my mistake

$ git fetch -q; echo $?
remote: Counting objects: 5, done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 3 (delta 1), reused 0 (delta 0)
Unpacking objects: 100% (3/3), done.
 From git@boss:sandbox
    b92d27c..17b8b5d  master     -> origin/master
0

These is the output when there is a change to be syncronized

BTW,  in crontab the commands are using -q option, the mistake was made 
just here :)


-- 
Richard Rossel
Softare Engineer at Airsage Inc.
Valparaiso - Chile

  reply	other threads:[~2009-12-14 16:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-14 14:45 git gc logs to standard error Richard Rossel
2009-12-14 15:55 ` Johan Herland
2009-12-14 16:04   ` Jacob Helwig
2009-12-14 16:23     ` Richard Rossel
2009-12-14 16:28       ` Jacob Helwig
2009-12-14 16:37         ` Richard Rossel [this message]
2009-12-14 16:46           ` Jacob Helwig
2009-12-14 16:10   ` Richard Rossel

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=4B2669CD.9020505@inf.utfsm.cl \
    --to=rrossel@inf.utfsm.cl \
    --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 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.