From: Quy Tonthat <qtonthat@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH] git-remote exclude
Date: Mon, 15 Jan 2007 01:57:26 +1100 [thread overview]
Message-ID: <45AA44D6.6080605@gmail.com> (raw)
"git-remote exclude" can be used to prevent one or more unwanted remote branches
from being tracked. After, for example,
$ git-remote origin exclude man html
"git-fetch origin" will no longer fetch origin/man and origin/html.
"git-remote exclude" does not check whether the "unwanted" branch
really exists on the remote repo.
Signed-off-by: Quy Tonthat <qtonthat@gmail.com>
---
git-remote.perl | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 51 insertions(+), 0 deletions(-)
diff --git a/git-remote.perl b/git-remote.perl
index fc055b6..8ee1bea 100755
--- a/git-remote.perl
+++ b/git-remote.perl
@@ -243,6 +243,47 @@ sub add_remote {
"+refs/heads/*:refs/remotes/$name/*");
}
+sub exclude_remote_branch {
+ my ($name, @branches) = @_;
+ if (!exists $remote->{$name}) {
+ print STDERR "remote $name does not exists.\n";
+ exit(1);
+ }
+
+ my $wildcard = "";
+ my %fetch_entries = ();
+ my @fetches = $git->command(qw(repo-config --get-all), "remote.$name.fetch");
+ foreach $fetch (@fetches) {
+ if ($fetch =~ m%^\+?refs/heads/\*:refs/remotes/$name/\*$%) {
+ $wildcard = $fetch;
+ }
+ else {
+ foreach $br (@branches) {
+ if ($fetch =~ m#^refs/heads/$br:.*$#) {
+ $fetch_entries{$br} = $fetch;
+ }
+ }
+ }
+ }
+
+ if (!$wildcard) {
+ print STDERR "No wildcard entry for $name. Config not changed\n";
+ exit(1);
+ }
+ my $clean;
+ ($clean = $wildcard) =~ s/([+*])/\\$1/g;
+ $git->command(qw(repo-config --unset), "remote.$name.fetch", $clean);
+ foreach $key (keys %fetch_entries) {
+ $git->command(qw(repo-config --unset), "remote.$name.fetch",
+ $fetch_entries{$key});
+ }
+ foreach $br (@branches) {
+ $git->command(qw(repo-config --add), "remote.$name.fetch",
+ "refs/heads/$br:");
+ }
+ $git->command(qw(repo-config --add), "remote.$name.fetch", $wildcard);
+}
+
if (!@ARGV) {
for (sort keys %$remote) {
print "$_\n";
@@ -274,9 +315,19 @@ elsif ($ARGV[0] eq 'add') {
}
add_remote($ARGV[1], $ARGV[2]);
}
+elsif ($ARGV[0] eq 'exclude') {
+ if (@ARGV < 3) {
+ print STDERR "Usage: git remote exclude <name> <branch>...\n";
+ exit(1);
+ }
+ my @branches = @ARGV;
+ shift(@branches); shift(@branches);
+ exclude_remote_branch($ARGV[1], @branches);
+}
else {
print STDERR "Usage: git remote\n";
print STDERR " git remote add <name> <url>\n";
+ print STDERR " git remote exclude <name> <branch>...\n";
print STDERR " git remote show <name>\n";
exit(1);
}
next reply other threads:[~2007-01-15 17:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-14 14:57 Quy Tonthat [this message]
2007-01-15 10:23 ` [PATCH] git-remote exclude Johannes Schindelin
2007-01-15 11:55 ` Andy Parkins
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=45AA44D6.6080605@gmail.com \
--to=qtonthat@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 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).