From: Pavel Roskin <proski@gnu.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git <git@vger.kernel.org>
Subject: Re: cg-pull to pull branches, not the whole repository
Date: Thu, 15 Sep 2005 23:09:41 -0400 [thread overview]
Message-ID: <1126840181.2387.8.camel@dv> (raw)
In-Reply-To: <7vu0gne25j.fsf@assigned-by-dhcp.cox.net>
On Wed, 2005-09-14 at 15:05 -0700, Junio C Hamano wrote:
> Pavel Roskin <proski@gnu.org> writes:
>
> > ... Unfortunately, listings are
> > still needed to get refs/tags and refs/heads. Any fix for that would
> > involve git core, and I don't see an elegant fix.
>
> All the necessary "core" support should already be there, except
> for the client side support. Please look at yesterday's thread
> with title "dumb transports not being welcomed".
Great. It looks like my concerns are fully understood and the work is
underway to address them. Sorry for the noise.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2005-09-16 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 21:31 cg-pull to pull branches, not the whole repository Pavel Roskin
2005-09-14 22:05 ` Junio C Hamano
2005-09-16 3:09 ` Pavel Roskin [this message]
2005-09-14 23:34 ` Petr Baudis
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=1126840181.2387.8.camel@dv \
--to=proski@gnu.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).