git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <johannes.sixt@telecom.at>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Clean up documentation that references deprecated 'git peek-remote'.
Date: Mon, 17 Dec 2007 16:11:55 -0800	[thread overview]
Message-ID: <7vy7bs50ac.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1197882503-4296-1-git-send-email-johannes.sixt@telecom.at> (Johannes Sixt's message of "Mon, 17 Dec 2007 10:08:23 +0100")

Johannes Sixt <johannes.sixt@telecom.at> writes:

> Now that 'git peek-remote' is deprecated and only an alias for
> 'git ls-remote', it should not be referenced from other manual pages.
>
> This also removes the description of the --exec option, which is no
> longer present.

It seems to be supported as a backward compatibility option but not
shown in the short help.  Removal of it from the documentation is
alright nevertheless.

Thanks.

      reply	other threads:[~2007-12-18  0:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17  9:08 [PATCH] Clean up documentation that references deprecated 'git peek-remote' Johannes Sixt
2007-12-18  0:11 ` 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=7vy7bs50ac.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.sixt@telecom.at \
    /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).