From: Quy Tonthat <qtonthat@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-remote exclude
Date: Thu, 18 Jan 2007 01:13:12 +1100 [thread overview]
Message-ID: <45AE2EF8.50403@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0701151118400.22628@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
> Hi,
>
> On Mon, 15 Jan 2007, Quy Tonthat wrote:
>
>> "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.
>
> That is not what your patch does.
>
> It rewrites the "remote.$name.fetch" entries so that those branches are
> not _updated_, but they are _fetched_ nevertheless.
I meant to say "track", but somehow "fetch" got to my fingers. Old ages, perhaps.
You are right, "update" is _the_ word. Thanks.
> 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.
For different situations, there are different paths to choose to reach that
ultimate "After All" (Zen? NO!). I offered one (little) path and expect to see
more of bigger ones. That's the _why_ (and/or, the _why_ not).
Quy
prev parent reply other threads:[~2007-01-17 14:13 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
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 [this message]
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=45AE2EF8.50403@gmail.com \
--to=qtonthat@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--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.