git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
To: Junio C Hamano <junkio@cox.net>
Cc: bonzini@gnu.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: [PATCH 1/3] git-branch: add --track and --no-track options
Date: Tue, 06 Mar 2007 08:23:26 +0100	[thread overview]
Message-ID: <45ED16EE.8020303@lu.unisi.ch> (raw)
In-Reply-To: <7v3b4jxtx8.fsf@assigned-by-dhcp.cox.net>


> Yes, that is correct.  Some C lib implementations seem to count
> %n and others don't so it is not reliable.  That is one of the
> reasons I personally have stayed away from fancier sscanf()
> constructs, both inside and outside git project.

So, should I remove it?  As I said, the code using sscanf is already the second try, and the first was utterly illegible, so I'd rather stay with it.

Paolo

  reply	other threads:[~2007-03-06  7:23 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
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 [this message]
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=45ED16EE.8020303@lu.unisi.ch \
    --to=paolo.bonzini@lu.unisi.ch \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=bonzini@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).