From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: "Carlos Rica" <jasampler@gmail.com>,
=?X-UNKNOWN?Q?Kristian_H=F8gsberg?= <krh@redhat.com>,
git@vger.kernel.org, "Julian Phillips" <julian@quantumfyre.co.uk>
Subject: git-fetch, was Re: [PATCH] Port git-tag.sh to C.
Date: Tue, 12 Jun 2007 13:41:50 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0706121341250.4059@racer.site> (raw)
In-Reply-To: <Pine.LNX.4.64.0706112314300.5848@iabervon.org>
Hi,
On Mon, 11 Jun 2007, Daniel Barkalow wrote:
> On Sat, 9 Jun 2007, Carlos Rica wrote:
>
> > Feel free to choose the script which you need to get replaced first,
> > or, depending on your urgency, you could ask me for one of them and I
> > would try to concentrate my efforts on it. Why do you started with
> > git-tag? For me, it was enough easy to begin with, perhaps you could
> > have other reasons.
>
> Incidentally, I have been working on fetch, based on Julian Phillips's
> version. I'm trying to split out the "how do I communicate with remote
> repositories" code, and use it for pushing and ls-remote as well as
> fetch. I've got a bunch of not-for-official-history development that you
> should look at if you try any of the remote-repository-access scripts.
How about pushing them onto repo.or.cz as a fork of git.git?
Ciao,
Dscho
next prev parent reply other threads:[~2007-06-12 12:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 22:45 [PATCH] Port git-tag.sh to C Kristian Høgsberg
2007-06-09 1:58 ` Carlos Rica
2007-06-12 3:28 ` Daniel Barkalow
2007-06-12 12:41 ` Johannes Schindelin [this message]
2007-06-12 13:29 ` git-fetch, was " Julian Phillips
2007-06-12 16:51 ` Daniel Barkalow
2007-06-12 23:55 ` Daniel Barkalow
2007-06-13 0:27 ` Johannes Schindelin
2007-06-09 18:26 ` Junio C Hamano
2007-06-09 23:27 ` Kristian Høgsberg
2007-06-10 12:37 ` Robin Rosenberg
2007-06-10 21:36 ` Junio C Hamano
2007-06-10 22:13 ` Jeff King
2007-06-10 22:19 ` Junio C Hamano
2007-06-10 22:22 ` Jeff King
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.0706121341250.4059@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=jasampler@gmail.com \
--cc=julian@quantumfyre.co.uk \
--cc=krh@redhat.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).