From: Paul Jackson <pj@engr.sgi.com>
To: azarah@nosferatu.za.org
Cc: raa.lkml@gmail.com, pasky@ucw.cz, git@vger.kernel.org
Subject: Re: Remove need to untrack before tracking new branch
Date: Thu, 14 Apr 2005 23:42:31 -0700 [thread overview]
Message-ID: <20050414234231.663fd7b3.pj@engr.sgi.com> (raw)
In-Reply-To: <1113543914.23299.151.camel@nosferatu.lan>
> No, '&' have a higher priority (weight?) than '&&'.
& has a higher precedence than &&
C Operator Precedence and Associativity
http://www.difranco.net/cop2220/op-prec.htm
and many others -- google for 'c operator precedence'
Where the bitops &, | and ^ bite you is that they are
lower precedence than many other ops, including '=='.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@engr.sgi.com> 1.650.933.1373, 1.925.600.0401
next prev parent reply other threads:[~2005-04-15 6:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050411135758.GA3524@pasky.ji.cz>
[not found] ` <1113310045.23299.15.camel@nosferatu.lan>
[not found] ` <20050412130250.GG22614@pasky.ji.cz>
[not found] ` <1113311595.23299.17.camel@nosferatu.lan>
[not found] ` <20050412132307.GH22614@pasky.ji.cz>
[not found] ` <1113375277.23299.25.camel@nosferatu.lan>
[not found] ` <20050413075441.GD16489@pasky.ji.cz>
[not found] ` <1113381672.23299.47.camel@nosferatu.lan>
[not found] ` <20050413092656.GO16489@pasky.ji.cz>
[not found] ` <1113394537.23299.51.camel@nosferatu.lan>
2005-04-13 22:19 ` Re: Re: Remove need to untrack before tracking new branch Petr Baudis
2005-04-14 6:55 ` Martin Schlemmer
2005-04-14 8:28 ` Martin Schlemmer
2005-04-14 8:38 ` Martin Schlemmer
2005-04-14 9:11 ` Petr Baudis
2005-04-14 9:40 ` Martin Schlemmer
2005-04-14 9:55 ` Martin Schlemmer
2005-04-14 22:35 ` Alex Riesen
2005-04-15 5:45 ` Martin Schlemmer
2005-04-15 6:42 ` Paul Jackson [this message]
2005-04-15 23:49 ` Alex Riesen
2005-04-14 22:42 ` Petr Baudis
2005-04-14 23:01 ` Martin Schlemmer
2005-04-14 23:00 ` Petr Baudis
2005-04-14 23:09 ` Martin Schlemmer
2005-04-14 23:25 ` Martin Schlemmer
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=20050414234231.663fd7b3.pj@engr.sgi.com \
--to=pj@engr.sgi.com \
--cc=azarah@nosferatu.za.org \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
--cc=raa.lkml@gmail.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).