From: Robin Rosenberg <robin.rosenberg@dewire.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/4] get_pathspec(): die when an out-of-tree path is given
Date: Fri, 7 Mar 2008 19:29:42 +0100 [thread overview]
Message-ID: <200803071929.42499.robin.rosenberg@dewire.com> (raw)
In-Reply-To: <1204879119-7528-2-git-send-email-gitster@pobox.com>
My gcc refuses to cooperate, giving me SEGV at line 666 or combine-diff, so
I'll ask instead of testing.
Do absolute paths to diff still work without exiting?
-- robin
next prev parent reply other threads:[~2008-03-07 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 8:38 [PATCH 0/4] Re-fix get_pathspec() Junio C Hamano
2008-03-07 8:38 ` [PATCH 1/4] get_pathspec(): die when an out-of-tree path is given Junio C Hamano
2008-03-07 18:29 ` Robin Rosenberg [this message]
2008-03-07 18:51 ` Junio C Hamano
2008-03-07 11:53 ` [PATCH 0/4] Re-fix get_pathspec() Johannes Schindelin
2008-03-07 17:48 ` Junio C Hamano
2008-03-08 9:37 ` 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=200803071929.42499.robin.rosenberg@dewire.com \
--to=robin.rosenberg@dewire.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).