From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Quy Tonthat <qtonthat@gmail.com>
Subject: Re: [PATCH] git-remote exclude
Date: Mon, 15 Jan 2007 11:55:23 +0000 [thread overview]
Message-ID: <200701151155.26111.andyparkins@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0701151118400.22628@wbgn013.biozentrum.uni-wuerzburg.de>
On Monday 2007 January 15 10:23, Johannes Schindelin wrote:
> But then, I don't really see _why_ you would want such a solution. After
> all, you are more likely to be interested in _specific_ branches, rather
> than all branches _except_ a few.
That's not true. I have a patch (that doesn't work, so it's not submitted),
that would allow me to have:
[remote "origin"]
url = git://git2.kernel.org/pub/scm/git/git.git
fetch = refs/heads/*:refs/remotes/up/*
fetch = !refs/heads/html
fetch = !refs/heads/todo
i.e. I don't want those two branches, but I do want everything else. I'd also
like to be able to do "!/refs/heads/temp/*" so I could block a whole
subdirectory of branches. I have a feeling that this would come in handy for
people like the person who was recently talking about having 880 branches in
his repository, with only a few active.
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com
next prev parent reply other threads:[~2007-01-15 17:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-14 14:57 [PATCH] git-remote exclude Quy Tonthat
2007-01-15 10:23 ` Johannes Schindelin
2007-01-15 11:55 ` Andy Parkins [this message]
2007-01-15 20:10 ` Jakub Narebski
2007-01-15 21:56 ` Junio C Hamano
2007-01-16 10:26 ` Andy Parkins
2007-01-16 11:16 ` Johannes Schindelin
2007-01-17 15:14 ` Quy Tonthat
2007-01-17 15:19 ` Johannes Schindelin
2007-01-17 14:13 ` Quy Tonthat
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=200701151155.26111.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=qtonthat@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).