git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: Deprecate git-fetch-pack?
Date: Sat, 10 Nov 2007 16:48:29 -0800	[thread overview]
Message-ID: <7v4pftip42.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0711101752490.29952@iabervon.org> (Daniel Barkalow's message of "Sat, 10 Nov 2007 18:11:53 -0500 (EST)")

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?

As to peek-remote, ls-remote over the native transport is a
synonym so I do not think anybody doing the scripting would have
problem doing s/peek-/ls-/ to their script, but again I do not
see a heavy maintenance burden to keep the synonym, yet.

  reply	other threads:[~2007-11-11  0:48 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 [this message]
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

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=7v4pftip42.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=barkalow@iabervon.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).