From: Junio C Hamano <gitster@pobox.com>
To: bonzini@gnu.org
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-fetch--tool and contrib/examples/git-fetch.sh
Date: Thu, 15 Nov 2007 21:16:15 -0800 [thread overview]
Message-ID: <7vzlxe22jk.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <473C45A8.7020903@lu.unisi.ch> (Paolo Bonzini's message of "Thu, 15 Nov 2007 14:12:08 +0100")
Paolo Bonzini <paolo.bonzini@lu.unisi.ch> writes:
> When git-fetch was builtin-ized the previous script was moved to
> contrib/examples. Now, it is the sole remaining user for most of
> git-parse-remote (except for get_remote_url) and for git-fetch--tool.
Yeah, moving them when they cease to be used to contrib/examples
would be a good thing to do.
prev parent reply other threads:[~2007-11-16 5:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 13:12 git-fetch--tool and contrib/examples/git-fetch.sh Paolo Bonzini
2007-11-16 5:16 ` Junio C Hamano [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=7vzlxe22jk.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=bonzini@gnu.org \
--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).