From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 7/2] Support for NO_OPENSSL
Date: Fri, 29 Jul 2005 21:17:24 -0700 [thread overview]
Message-ID: <7v7jf96i7f.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0507292038160.29650@g5.osdl.org> (Linus Torvalds's message of "Fri, 29 Jul 2005 20:39:56 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> This doesn't work at least in the form that Junio merged it (and from
> what I can tell, he merged your patch as-is):
Slipped my filter. Sorry. Will fix.
next prev parent reply other threads:[~2005-07-30 4:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 8:58 [PATCH 0/2] Bits from git-pb Petr Baudis
2005-07-29 9:00 ` [PATCH 1/2] Trivial tidyups Petr Baudis
2005-07-29 9:01 ` [PATCH 2/2] Unify usage strings declaration Petr Baudis
2005-07-30 2:11 ` Junio C Hamano
2005-07-30 6:03 ` Matthias Urlichs
2005-07-29 12:53 ` [PATCH 3/2] git-merge-cache -q doesn't complain about failing merge program Petr Baudis
2005-07-30 2:11 ` Junio C Hamano
2005-07-29 15:48 ` [PATCH 4/2] Improve the compilation-time settings interface Petr Baudis
2005-07-29 18:23 ` Petr Baudis
2005-07-29 15:48 ` [PATCH 5/2] Remove the explicit Makefile dependencies description Petr Baudis
2005-07-29 15:50 ` [PATCH 6/2] Reorder Makefile rules Petr Baudis
2005-07-29 15:50 ` [PATCH 7/2] Support for NO_OPENSSL Petr Baudis
2005-07-30 3:39 ` Linus Torvalds
2005-07-30 4:17 ` Junio C Hamano [this message]
2005-07-30 5:02 ` [PATCH] Under NO_OPENSSL -lssl should not be used Junio C Hamano
2005-07-30 16:09 ` Linus Torvalds
2005-08-02 22:43 ` Jon Seymour
2005-07-29 17:21 ` [PATCH 8/2] Build commands through object files Petr Baudis
2005-07-30 10:31 ` [PATCH 0/2] Bits from git-pb Petr Baudis
2005-07-30 17:33 ` Junio C Hamano
2005-07-30 17:59 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v7jf96i7f.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).