From: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] git-branch: add --track and --no-track options
Date: Mon, 05 Mar 2007 18:22:24 +0100 [thread overview]
Message-ID: <45EC51D0.7000406@lu.unisi.ch> (raw)
In-Reply-To: <Pine.LNX.4.63.0703051701331.22628@wbgn013.biozentrum.uni-wuerzburg.de>
>>>> + /* Try an exact match first. */
>>>> + sscanf(value, "refs/%*[^:]:%n", &len_first);
>>> This is the first time I saw that sscanf format type. How portable is it?
>> It is. At the very least it is in OpenGroup.
>
> That is not very reassuring for me. However, I learnt something new about
> sscanf(), so it was not lost on me.
Google books reveals that it's called a "scanset" (I didn't know that either). I found it in "C: The Complete Reference" by Herb Schildt (2000) and "POSIX Programmer's Guide" by D.A. Lewine (1991). I don't have K&R at hand to check.
Paolo
next prev parent reply other threads:[~2007-03-05 17:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 8:57 [PATCH 1/3] git-branch: add --track and --no-track options Paolo Bonzini
2007-03-05 14:50 ` Johannes Schindelin
2007-03-05 15:22 ` Paolo Bonzini
2007-03-05 16:09 ` Johannes Schindelin
2007-03-05 17:22 ` Paolo Bonzini [this message]
2007-03-05 15:36 ` Paolo Bonzini
2007-03-05 15:58 ` Johannes Schindelin
2007-03-05 16:54 ` Paolo Bonzini
2007-03-05 17:16 ` Johannes Schindelin
2007-03-05 17:22 ` Paolo Bonzini
2007-03-05 18:37 ` Johannes Schindelin
2007-03-05 21:19 ` Paolo Bonzini
2007-03-05 21:27 ` Junio C Hamano
2007-03-06 7:23 ` Paolo Bonzini
2007-03-05 23:09 ` Johannes Schindelin
2007-03-06 6:45 ` Junio C Hamano
2007-03-06 7:26 ` Paolo Bonzini
2007-03-06 7:40 ` Junio C Hamano
2007-03-06 7:48 ` Paolo Bonzini
2007-03-06 8:22 ` Junio C Hamano
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=45EC51D0.7000406@lu.unisi.ch \
--to=paolo.bonzini@lu.unisi.ch \
--cc=Johannes.Schindelin@gmx.de \
--cc=bonzini@gnu.org \
--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.