From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 2/3] git-fetch: do not use "*" for fetching multiple refs
Date: Wed, 06 Dec 2006 19:27:00 +0100 [thread overview]
Message-ID: <el71tj$edm$1@sea.gmane.org> (raw)
In-Reply-To: 1165429001.993.35.camel@ibook.zvpunry.de
Michael Loeffler wrote:
>> We could use perl for that, but embedded perl is a bit horrible.
>
> I had the same idea after the sed problems with macos/solaris, but
> embedded perl is really a bit horrible.
Or you can rewrite git-fetch in Perl (or as built-in in C).
> I would prefer the following ways to do this globfetch stuff:
>
> 1.) The original refspec:
> Pull: refs/heads/master:refs/remotes/origin/master
>
> 2.) The one with "prefix match":
> Pull: refs/heads/:refs/remotes/origin/
I just worry what would happen when someone would write e.g.
Pull: refs/heads/:refs/heads/origin-
> 3.) The one with extended regex:
> Pull: refs/heads/(.*):refs/remotes/origin/\1
3.) The one with shell-like (fnmatch / glob) globbing
Pull: refs/heads/*:refs/remotes/origin/*
By the way, with globbing we really need some other way than
first Pull: line to select remote head to merge on "git pull".
For example "Merge:" line / remote.<name>.merge config var.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-12-06 18:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 19:38 [PATCH 2/3] git-fetch: do not use "*" for fetching multiple refs Michael Loeffler
2006-12-04 19:48 ` Jakub Narebski
2006-12-06 16:34 ` Michael Loeffler
2006-12-06 16:58 ` Jakub Narebski
2006-12-06 18:16 ` Michael Loeffler
2006-12-06 18:27 ` Jakub Narebski [this message]
2006-12-06 18:39 ` Junio C Hamano
2006-12-06 18:37 ` Junio C Hamano
2006-12-06 23:21 ` Johannes Schindelin
2006-12-06 23:38 ` Jakub Narebski
2006-12-04 19:49 ` Michael Loeffler
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='el71tj$edm$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.