From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-send-pack: broken handling of ref specs with wildcards
Date: Thu, 7 Jun 2007 23:56:56 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0706072356220.4046@racer.site> (raw)
In-Reply-To: <20070607225302.GA10633@steel.home>
Hi,
On Fri, 8 Jun 2007, Alex Riesen wrote:
> Try something like this:
>
> git-send-pack --remote=origin --thin /some/other/repo \
> 'refs/heads/*:refs/remotes/child/*'
>
> The result looks broken: the sent reference are created not in
> refs/remotes/child/ but just in refs/heads/ of /some/other/repo.
I had the impression that it was git-push, a porcelain, which handles
refspec wildcards, not send-pack, which is plumbing.
Ciao,
Dscho
next prev parent reply other threads:[~2007-06-07 22:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 22:53 git-send-pack: broken handling of ref specs with wildcards Alex Riesen
2007-06-07 22:56 ` Johannes Schindelin [this message]
2007-06-08 6:33 ` Junio C Hamano
2007-06-08 18:47 ` Daniel Barkalow
2007-06-07 23:43 ` [PATCH] Fix push with refspecs containing wildcards Alex Riesen
2007-06-08 6:38 ` Junio C Hamano
2007-06-08 7:42 ` Junio C Hamano
2007-06-08 9:13 ` Alex Riesen
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.0706072356220.4046@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.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).