From: "Kyle J. McKay" <mackyle@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH v4 0/2] allow git-svn fetching to work using serf
Date: Thu, 18 Jul 2013 17:16:44 -0700 [thread overview]
Message-ID: <ACCFF6B2-010B-465A-A011-E56BCE64C119@gmail.com> (raw)
In-Reply-To: <7v8v131lye.fsf@alter.siamese.dyndns.org>
On Jul 18, 2013, at 16:34, Junio C Hamano wrote:
> "Kyle J. McKay" <mackyle@gmail.com> writes:
>
>> This patch allows git-svn to fetch successfully using the
>> serf library when given an https?: url to fetch from.
>> ...
>> Versions v2-v3 of the patch introduced a bug when attempting
>> to change the _temp_cache function to use the new
>> temp_is_locked function at the suggestion of a reviewer.
>
> Err, excuse me, is this meant to _replace_ what is already in 'next'
> for the past 6 days?
>
> Could you feed an incremental update, highlighting where the update
> improves compared to the previous attempt in the log message?
OK. I have sent out an "incremental update against 'next' branch'"
patch based on how a set of recent incremental updates to 'next' was
sent to the list on 2013-07-04. If that is not what you had in mind,
I apologize in advance.
prev parent reply other threads:[~2013-07-19 0:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 19:15 [PATCH v4 0/2] allow git-svn fetching to work using serf Kyle J. McKay
2013-07-18 19:15 ` [PATCH v4 1/2] Git.pm: add new temp_is_locked function Kyle J. McKay
2013-07-18 19:15 ` [PATCH v4 2/2] git-svn: allow git-svn fetching to work using serf Kyle J. McKay
2013-07-18 19:29 ` Jonathan Nieder
2013-07-18 23:31 ` Kyle J. McKay
2013-07-18 23:40 ` Eric Wong
2013-07-18 23:34 ` [PATCH v4 0/2] " Junio C Hamano
2013-07-19 0:16 ` Kyle J. McKay [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
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=ACCFF6B2-010B-465A-A011-E56BCE64C119@gmail.com \
--to=mackyle@gmail.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.
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).