git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Push code for transport library
Date: Sun, 8 Jul 2007 21:29:18 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707082128290.4248@racer.site> (raw)
In-Reply-To: <Pine.LNX.4.64.0707081608100.6977@iabervon.org>

Hi,

On Sun, 8 Jul 2007, Daniel Barkalow wrote:

> This moves the code to call push backends into a library that can be 
> extended to make matching fetch and push decisions based on the URL it 
> gets, and which could be changed to have built-in implementations 
> instead of calling external programs.

I do not have time to look at the patch more closely, but I like the 
direction this takes very much.

Thanks,
Dscho

  reply	other threads:[~2007-07-08 20:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08 20:09 [PATCH] Push code for transport library Daniel Barkalow
2007-07-08 20:29 ` Johannes Schindelin [this message]
2007-07-08 21:14 ` Shawn O. Pearce

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.0707082128290.4248@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).