From: Linus Torvalds <torvalds@osdl.org>
To: Timo Hirvonen <tihirvon@gmail.com>
Cc: junkio@cox.net, matled@gmx.net, git@vger.kernel.org, paulus@samba.org
Subject: Re: [PATCH] Fix filename verification when in a subdirectory
Date: Wed, 26 Apr 2006 11:14:00 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0604261112240.3701@g5.osdl.org> (raw)
In-Reply-To: <20060426210541.5e145e88.tihirvon@gmail.com>
On Wed, 26 Apr 2006, Timo Hirvonen wrote:
>
> Extra semicolon.
Duh, indeed. It just didn't show up in any of the normal cases.
Junio, just apply without that stupid semicolon..
Linus
prev parent reply other threads:[~2006-04-26 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-23 12:03 lstat() call in rev-parse.c Paul Mackerras
2006-04-23 16:19 ` Linus Torvalds
2006-04-24 23:23 ` Paul Mackerras
2006-04-26 15:28 ` Matthias Lederhofer
2006-04-26 15:43 ` Linus Torvalds
2006-04-26 17:15 ` [PATCH] Fix filename verification when in a subdirectory Linus Torvalds
2006-04-26 18:05 ` Timo Hirvonen
2006-04-26 18:14 ` Linus Torvalds [this message]
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=Pine.LNX.4.64.0604261112240.3701@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=matled@gmx.net \
--cc=paulus@samba.org \
--cc=tihirvon@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).