From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Limit filename for format-patch
Date: Fri, 23 Feb 2007 22:39:18 +0100 [thread overview]
Message-ID: <200702232239.19504.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0702230143370.22628@wbgn013.biozentrum.uni-wuerzburg.de>
fredag 23 februari 2007 01:49 skrev Johannes Schindelin:
> Hi,
>
> I agree that your patch fixes a long-time issue.
>
> On Fri, 23 Feb 2007, Robin Rosenberg wrote:
>
> > + if (strlen(output_directory) > sizeof filename - suffix_len)
>
> I know that "sizeof filename" works, but in git.git, `git grep sizeof'
> returns > 700 instances, only 23 of which do not use the
> "sizeof(filename)" form. It's just a style issue, but I prefer the latter
> nevertheless...
Actually there are (only) about 500 of them that are not the sizeof(type) kind.
I prefer not to use extra parentheses except for grouping complex expressions
for readability.
> > for (j = 0;
>
> Does this:
>
> > + j< 64-suffix_len-5 &&
> > len < sizeof(filename) - suffix_len &&
> > sol[j] && sol[j] != '\n';
> > j++) {
>
> not make this:
>
> > + if (len + strlen(fmt_patch_suffix) >= sizeof filename)
> > + return error("Patch pathname too long");
>
> unnecessary for the case that there _was_ an output directory specified?
> I'd make that an "else if"... But I might be missing something.
The last statement errs out if the total length is too long which is a different
issue than truncating the patch name. There is no reason to two paths when
one does perfectly well. But I could replace strlen there.
-- robin
next prev parent reply other threads:[~2007-02-23 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 0:37 [PATCH] Limit filename for format-patch Robin Rosenberg
2007-02-23 0:49 ` Johannes Schindelin
2007-02-23 21:39 ` Robin Rosenberg [this message]
2007-02-23 21:47 ` Robin Rosenberg
2007-02-23 22:27 ` Robin Rosenberg
2007-02-24 1:27 ` Johannes Schindelin
2007-02-24 1:33 ` Junio C Hamano
2007-02-24 8:51 ` Junio C Hamano
2007-02-24 11:24 ` Robin Rosenberg
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=200702232239.19504.robin.rosenberg@dewire.com \
--to=robin.rosenberg@dewire.com \
--cc=Johannes.Schindelin@gmx.de \
--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 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).