From: Jakub Narebski <jnareb@gmail.com>
To: jidanni@jidanni.org
Cc: git@vger.kernel.org
Subject: Re: fetch branch blacklist
Date: Fri, 09 Jan 2009 12:23:08 -0800 (PST) [thread overview]
Message-ID: <m3wsd41b7q.fsf@localhost.localdomain> (raw)
In-Reply-To: <87r63ek6cw.fsf@jidanni.org>
jidanni@jidanni.org writes:
> If one wants to always fetch all except one remote branch, one cannot
> just blacklist it, but must instead whitelist all the rest.
> $ git branch -rd origin/man origin/html
> Deleted remote branch origin/man.
> Deleted remote branch origin/html.
> Plus I edited them out of FETCH_HEAD. Nonetheless, back from the dead:
> $ git pull
> From git://git.kernel.org/pub/scm/git/git
> * [new branch] html -> origin/html
> * [new branch] man -> origin/man
> The only solution is to change .git/config:
> [remote "origin"]
> url = git://git.kernel.org/pub/scm/git/git.git
> # fetch = +refs/heads/*:refs/remotes/origin/*
> fetch = +refs/heads/maint:refs/remotes/origin/maint
> fetch = +refs/heads/master:refs/remotes/origin/master
> fetch = +refs/heads/next:refs/remotes/origin/next
> fetch = +refs/heads/pu:refs/remotes/origin/pu
> fetch = +refs/heads/todo:refs/remotes/origin/todo
Well, you can always use hooks for that (see for example
underdocumented contrib/hooks/update-paranoid)... or you can try to
scratch that itch yourself. gitignore supports inverse (negated)
patterns (!<pattern>), so there is some code dealing with
"blacklisting". I would propose using the same '!' character, or
perhaps one of forbidden characters (see git-check-ref-format(1)),
i.e.
[remote "origin"]
url = git://git.kernel.org/pub/scm/git/git.git
fetch = +refs/heads/*:refs/remotes/origin/*
fetch = !refs/heads/html
fetch = !refs/heads/man
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-01-09 20:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 0:07 fetch branch blacklist jidanni
2009-01-09 20:23 ` Jakub Narebski [this message]
2009-01-10 2:30 ` jidanni
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=m3wsd41b7q.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jidanni@jidanni.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.