From: Matthias Lederhofer <matled@gmx.net>
To: Andy Parkins <andyparkins@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] tone down the detached head warning
Date: Thu, 1 Feb 2007 13:48:00 +0100 [thread overview]
Message-ID: <20070201124800.GA3863@moooo.ath.cx> (raw)
In-Reply-To: <200702010844.34500.andyparkins@gmail.com>
Andy Parkins <andyparkins@gmail.com> wrote:
> On Thursday 2007 February 01 00:14, Jakub Narebski wrote:
>
> > Although the fact that clone copies all branches and tags (I don't think
> > there is a way to clone only subset of branches), and that fetch is multi
>
> There is, as long as you are willing to organise your branches in a consistent
> way. I keep all my branches with the prefix "ap/" then on another
> development machine I just have
>
> pull = refs/heads/ap/*:refs/heads/up/ap/*
>
> In my config. This means I can make local branches that won't be grabbed
> during the fetch, but still have branches automatically exported.
>
> This actually highlights a weakness in the globbing. There is no way, for
> example, to grab only unprefixed branches because the glob is blind to path
> dividers (as is usual). What would be even better would be a two glob
> symbols, one meaning "do cross separators", one meaning "don't". I think
> rsync solves it for it's include/exclude patterns with a double asterisk.
> That is:
>
> rsync -av --exclude "foo/*/bar" src/ dest/
>
> Would exclude anything called "bar" two levels under "foo/"; wheras
>
> rsync -av --exclude "foo/**/bar" src/ dest/
>
> Would exclude anything called "bar" anywhere deeper than two levels
> under "foo".
>
> I haven't thought of a good way of applying this in git though, and I have a
> feeling that it could just complicate things excessively.
fnmatch with FNM_PATHNAME disables * to match on / but it does not
support the ** syntax afaik.
next prev parent reply other threads:[~2007-02-01 12:48 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 19:10 [PATCH] tone down the detached head warning Nicolas Pitre
2007-01-31 23:19 ` Jeff King
2007-01-31 23:25 ` Jakub Narebski
2007-01-31 23:27 ` Jeff King
2007-01-31 23:33 ` Jakub Narebski
2007-01-31 23:54 ` Carl Worth
2007-02-01 0:14 ` Jakub Narebski
2007-02-01 8:44 ` Andy Parkins
2007-02-01 12:48 ` Matthias Lederhofer [this message]
2007-02-01 0:11 ` Nicolas Pitre
2007-02-01 3:00 ` Jeff King
2007-02-01 3:23 ` Junio C Hamano
2007-02-01 3:29 ` Jeff King
2007-02-01 3:47 ` Nicolas Pitre
2007-02-01 3:54 ` Jeff King
2007-02-01 9:08 ` [PATCH] detached HEAD -- finishing touches Junio C Hamano
2007-02-01 9:46 ` Raimund Bauer
2007-02-01 9:53 ` Alex Riesen
2007-02-01 9:54 ` Alex Riesen
2007-02-01 18:44 ` [PATCH] git-checkout: disable guides how to switch branches with ui.guide Matthias Lederhofer
2007-02-01 20:42 ` Junio C Hamano
2007-02-01 20:51 ` Matthias Lederhofer
2007-02-01 21:06 ` Junio C Hamano
2007-02-01 21:23 ` Matthias Lederhofer
2007-02-01 21:34 ` Carl Worth
2007-02-01 21:59 ` Nicolas Pitre
2007-02-01 22:16 ` Carl Worth
2007-02-01 23:18 ` Jakub Narebski
2007-02-01 21:52 ` [PATCH] detached HEAD -- finishing touches Theodore Tso
2007-02-02 1:11 ` Junio C Hamano
2007-02-02 1:16 ` Theodore Tso
2007-02-02 1:27 ` Carl Worth
2007-02-02 1:30 ` Junio C Hamano
2007-02-02 1:46 ` Carl Worth
2007-02-02 2:38 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070201124800.GA3863@moooo.ath.cx \
--to=matled@gmx.net \
--cc=andyparkins@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).