Re: BUG: "git checkout -q -b foo origin/foo" is not quiet

2017-02-06 Thread Kevin Layer 
Yeah, my bad.  I was confused.  Sorry for the noise.

On Fri, Feb 3, 2017 at 4:55 PM, Cornelius Weig
 wrote:
> On 02/03/2017 10:36 PM, Kevin Layer wrote:
>> Note that git version 1.8.3.1 is quiet and does not print the
>> "tracking remote" message.
>
> So what you are saying is, that git v1.8.3.1 *is* quiet, but v1.7.1 is
> not? Sounds like a fixed bug to me.
>
> I also checked with the latest version and it did not print anything
> when used with -q.
>
>
> You seem to urgently need quiet branch creation. Have you thought about
> dumping unwanted output in the shell? E.g. in bash
>
> $ git whatever >&/dev/null

Re: BUG: "git checkout -q -b foo origin/foo" is not quiet

2017-02-03 Thread Cornelius Weig 
On 02/03/2017 10:36 PM, Kevin Layer wrote:
> Note that git version 1.8.3.1 is quiet and does not print the
> "tracking remote" message.

So what you are saying is, that git v1.8.3.1 *is* quiet, but v1.7.1 is
not? Sounds like a fixed bug to me.

I also checked with the latest version and it did not print anything
when used with -q.


You seem to urgently need quiet branch creation. Have you thought about
dumping unwanted output in the shell? E.g. in bash

$ git whatever >&/dev/null

Re: BUG: "git checkout -q -b foo origin/foo" is not quiet

2017-02-03 Thread Kevin Layer 
Note that git version 1.8.3.1 is quiet and does not print the
"tracking remote" message.

On Fri, Feb 3, 2017 at 10:20 AM, Kevin Layer  wrote:
> $ git checkout -q -b foo origin/foo
> Branch foo set up to track remote branch foo from origin.
>
> I said -q because I didn't want *any* output.
>
> I looked at the git sources, on the maint branch, and it appears to
> still be the case.
> I see this behavior on 1.7.1.
>
> Kevin

BUG: "git checkout -q -b foo origin/foo" is not quiet

2017-02-03 Thread Kevin Layer 
$ git checkout -q -b foo origin/foo
Branch foo set up to track remote branch foo from origin.

I said -q because I didn't want *any* output.

I looked at the git sources, on the maint branch, and it appears to
still be the case.
I see this behavior on 1.7.1.

Kevin