From: Mike Hommey <mh@glandium.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Daniel Barkalow <barkalow@iabervon.org>, git@vger.kernel.org
Subject: Re: Deprecate git-fetch-pack?
Date: Sun, 11 Nov 2007 09:32:57 +0100 [thread overview]
Message-ID: <20071111083257.GB14474@glandium.org> (raw)
In-Reply-To: <7v4pftip42.fsf@gitster.siamese.dyndns.org>
On Sat, Nov 10, 2007 at 04:48:29PM -0800, Junio C Hamano wrote:
> Daniel Barkalow <barkalow@iabervon.org> writes:
>
> > Now that git-fetch is in C, built in, and doing the fetch-pack in the same
> > process, the normal usage patterns don't involve actually executing
> > git-fetch-pack. Can we deprecate it at this point, or it is plausibly
> > being used by scripts? As it is now, I'm not entirely confidant that the
> > tests in t5500 won't be fooled by git-fetch working even with
> > git-fetch-pack being broken in various ways, which should be fixed if we
> > want to keep it.
> >
> > We also might as well deprecate peek-remote now that it's a synonym for
> > ls-remote.
>
> Especially because git-fetch is no longer as hackable as it used
> to be, and because people may still find special needs that can
> be hacked up with direct access to low level transports from the
> script more easily than going down to the C level, I'd rather
> wait and see for a cycle or two to decide. There is no strong
> reason to drop it, is there?
Still, if the functionality is needed, i think it would be better if it
were provided by git-fetch --pack. The list of programs is already long
enough, it should be time to shrink it.
Mike
prev parent reply other threads:[~2007-11-11 8:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 23:11 Deprecate git-fetch-pack? Daniel Barkalow
2007-11-11 0:48 ` Junio C Hamano
2007-11-11 3:09 ` Ask Bjørn Hansen
2007-11-11 11:05 ` Johannes Schindelin
2007-11-11 21:16 ` Junio C Hamano
2007-11-11 22:21 ` Theodore Tso
2007-11-11 22:35 ` Junio C Hamano
2007-11-11 22:50 ` Johannes Schindelin
2007-11-11 23:58 ` Theodore Tso
2007-11-12 0:16 ` Jakub Narebski
2007-11-12 17:29 ` Jon Loeliger
2007-11-12 17:33 ` Johannes Schindelin
2007-11-12 18:56 ` Jon Loeliger
2007-11-12 19:08 ` Johannes Schindelin
2007-11-12 19:16 ` Jon Loeliger
2007-11-12 0:57 ` [PATCH,RFC 1/2] Make the list of common commands more exclusive Theodore Ts'o
2007-11-12 0:57 ` [PATCH,RFC 2/2] Remove hint to use "git help -a" Theodore Ts'o
2007-11-12 2:21 ` [PATCH,RFC 1/2] Make the list of common commands more exclusive Junio C Hamano
2007-11-12 5:48 ` Ping Yin
2007-11-12 6:22 ` Theodore Tso
2007-11-12 7:26 ` Junio C Hamano
2007-11-12 10:24 ` Mike Hommey
2007-11-12 12:23 ` Johannes Schindelin
2007-11-12 7:57 ` Ask Bjørn Hansen
2007-11-12 10:21 ` Andreas Ericsson
2007-11-12 15:20 ` Theodore Tso
2007-11-12 10:15 ` Deprecate git-fetch-pack? Andreas Ericsson
2007-11-12 1:10 ` Ask Bjørn Hansen
2007-11-11 8:32 ` Mike Hommey [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=20071111083257.GB14474@glandium.org \
--to=mh@glandium.org \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).