From: "McMullan, Jason" <jason.mcmullan@timesys.com>
To: "Daniel Barkalow" <barkalow@iabervon.org>
Cc: "Linus Torvalds" <torvalds@osdl.org>,
"Petr Baudis" <pasky@ucw.cz>, "Junio C Hamano" <junkio@cox.net>,
"GIT Mailling list" <git@vger.kernel.org>
Subject: Re: [PATCH 3/4] Generic support for pulling refs
Date: Tue, 07 Jun 2005 09:18:56 -0400
Date: Tue, 7 Jun 2005 09:11:54 -0400 [thread overview]
Message-ID: <1118150337.8970.49.camel@jmcmullan.timesys> (raw)
In-Reply-To: <Pine.LNX.4.21.0506061635070.30848-100000@iabervon.org>
[-- Attachment #1: Type: text/plain, Size: 531 bytes --]
On Mon, 2005-06-06 at 16:38 -0400, Daniel Barkalow wrote:
> This adds support to pull.c for requesting a reference and writing it to a
> file. All of the git-*-pull programs get stubs for now.
>
> [snip snip]
Well, looks like you beat me to the punch, Daniel!
I hereby concede the Deathmatch to git-ssh-pu{sh,ll}, and withdraw
git-sync from consideration.
Way to go Daniel!
"Welcome to Git Thunderdome. Two codes enter, one code leaves."
--
Jason McMullan <jason.mcmullan@timesys.com>
TimeSys Corporation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-07 13:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 20:27 [PATCH 0/4] Writing refs in git-ssh-push Daniel Barkalow
2005-06-06 20:31 ` [PATCH 1/4] Operations on refs Daniel Barkalow
2005-06-06 20:35 ` [PATCH 2/4] rsh.c environment variable Daniel Barkalow
2005-06-06 20:38 ` [PATCH 3/4] Generic support for pulling refs Daniel Barkalow
2005-06-07 13:18 ` McMullan, Jason [this message]
2005-06-07 16:45 ` Daniel Barkalow
2005-06-06 20:43 ` [PATCH 4/4] -w support for git-ssh-pull/push Daniel Barkalow
2005-06-07 3:17 ` [PATCH 0/4] Writing refs in git-ssh-push Linus Torvalds
2005-06-07 5:22 ` Daniel Barkalow
2005-06-07 5:54 ` Frank Sorenson
2005-06-07 7:30 ` Thomas Glanzmann
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=1118150337.8970.49.camel@jmcmullan.timesys \
--to=jason.mcmullan@timesys.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pasky@ucw.cz \
--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.
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).