1 <?xml version="1.0" encoding="UTF-8"?>
\r
2 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
\r
4 <article lang="en" id="git-peek-remote(1)">
\r
6 <title>git-peek-remote(1)</title>
\r
8 <primary>git-peek-remote(1)</primary>
\r
11 <simplesect id="_name">
\r
13 <simpara>git-peek-remote - List the references in a remote repository</simpara>
\r
15 <simplesect id="_synopsis">
\r
16 <title>SYNOPSIS</title>
\r
18 <literallayout><emphasis>git peek-remote</emphasis> [--upload-pack=<git-upload-pack>] [<host>:]<directory></literallayout>
\r
21 <simplesect id="_description">
\r
22 <title>DESCRIPTION</title>
\r
23 <simpara>This command is deprecated; use <emphasis>git ls-remote</emphasis> instead.</simpara>
\r
25 <simplesect id="_options">
\r
26 <title>OPTIONS</title>
\r
30 --upload-pack=<git-upload-pack>
\r
34 Use this to specify the path to <emphasis>git-upload-pack</emphasis> on the
\r
35 remote side, if it is not found on your $PATH. Some
\r
36 installations of sshd ignores the user's environment
\r
37 setup scripts for login shells (e.g. .bash_profile) and
\r
38 your privately installed git may not be found on the system
\r
39 default $PATH. Another workaround suggested is to set
\r
40 up your $PATH in ".bashrc", but this flag is for people
\r
41 who do not want to pay the overhead for non-interactive
\r
42 shells, but prefer having a lean .bashrc file (they set most of
\r
43 the things up in .bash_profile).
\r
53 A remote host that houses the repository. When this
\r
54 part is specified, <emphasis>git-upload-pack</emphasis> is invoked via
\r
65 The repository to sync from.
\r
71 <simplesect id="_git">
\r
73 <simpara>Part of the <xref linkend="git(1)" /> suite</simpara>
\r