git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: martin f krafft <madduck@madduck.net>
To: git discussion list <git@vger.kernel.org>
Subject: git-svn patch faulty (was: failing to send patches to the list)
Date: Fri, 13 Jul 2007 11:56:44 +0200	[thread overview]
Message-ID: <20070713095644.GA26743@lapse.madduck.net> (raw)
In-Reply-To: <20070713093050.GA18001@lapse.madduck.net>

[-- Attachment #1: Type: text/plain, Size: 762 bytes --]

Hi there,

still not having figured out the problem with the list (and I did
contact postmaster@), I just discovered that in fact the patch only
handles git-svn clone, not git-svn init. Thus, it's best to ignore
it for now. I am sorry for not taking enough care before publishing
it.

The openssl-autodetect patch does work and is ready for inclusion,
if you agree.

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
 
spamtraps: madduck.bogus@madduck.net
 
"if builders built buildings the way
 programmers wrote programs,
 then the first woodpecker that came along
 would destroy civilization."
                                                  -- gerald weinberg

[-- Attachment #2: Digital signature (GPG/PGP) --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-07-13  9:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-13  9:30 failing to send patches to the list martin f krafft
2007-07-13  9:56 ` martin f krafft [this message]
2007-07-14 10:54   ` git-svn patch faulty (was: failing to send patches to the list) Eric Wong
2007-07-13 12:57 ` failing to send patches to the list Alex Riesen
2007-07-14  6:05   ` martin f krafft
2007-07-13 15:55 ` Jeff King
2007-07-14  6:52   ` martin f krafft
2007-07-14  0:58 ` Jakub Narebski
2007-07-14  6:59   ` martin f krafft

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=20070713095644.GA26743@lapse.madduck.net \
    --to=madduck@madduck.net \
    --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).