Should We Keep or Drop the Bottom Toolbar? Post: 302681857

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

HP-UX toolbar help

Hi all, I am trying to set some icons in the toolbar thingy (HP-UX 10.2). I used the Toolboxes->Personal to help me setup, but it put the program icon in the personal toolbox folder. So I dragged it out to the Desktop. Now I've a link on a Desktop. Any ideas on how to create directly on to...

2. UNIX and Linux Applications

Showing all open programs on your bottom toolbar

http://i255.photobucket.com/albums/hh133/COKEDUDEUSF/toolbar.jpg Take a look at my picture to understand what I'm talking about. I have a bunch of programs open right now and I can't see the name of the programs on my toolbar. Is there hopefully a way to see all open programs on your toolbar...

3. What is on Your Mind?

Change Toolbar to Opt In?

Hey! I'm thinking we should change the toolbar to "opt in" and have it off for members by default? But then, the would not have toolbar access to the code tag videos, etc. so then I thought to make it "opt in" after say 30 posts. That way, the toolbar will show to all new users with less...

LEARN ABOUT DEBIAN

git-ls-remote

GIT-LS-REMOTE(1)						    Git Manual							  GIT-LS-REMOTE(1)

NAME

       git-ls-remote - List references in a remote repository

SYNOPSIS

       git ls-remote [--heads] [--tags]  [-u <exec> | --upload-pack <exec>]
		     [--exit-code] <repository> [<refs>...]

DESCRIPTION

       Displays references available in a remote repository along with the associated commit IDs.

OPTIONS

       -h, --heads, -t, --tags
	   Limit to only refs/heads and refs/tags, respectively. These options are not mutually exclusive; when given both, references stored in
	   refs/heads and refs/tags are displayed.

       -u <exec>, --upload-pack=<exec>
	   Specify the full path of git-upload-pack on the remote host. This allows listing references from repositories accessed via SSH and
	   where the SSH daemon does not use the PATH configured by the user.

       --exit-code
	   Exit with status "2" when no matching refs are found in the remote repository. Usually the command exits with status "0" to indicate it
	   successfully talked with the remote repository, whether it found any matching refs.

       <repository>
	   Location of the repository. The shorthand defined in $GIT_DIR/branches/ can be used. Use "." (dot) to list references in the local
	   repository.

       <refs>...
	   When unspecified, all references, after filtering done with --heads and --tags, are shown. When <refs>... are specified, only
	   references matching the given patterns are displayed.

EXAMPLES

	   $ git ls-remote --tags ./.
	   d6602ec5194c87b0fc87103ca4d67251c76f233a	   refs/tags/v0.99
	   f25a265a342aed6041ab0cc484224d9ca54b6f41	   refs/tags/v0.99.1
	   7ceca275d047c90c0c7d5afb13ab97efdf51bd6e	   refs/tags/v0.99.3
	   c5db5456ae3b0873fc659c19fafdde22313cc441	   refs/tags/v0.99.2
	   0918385dbd9656cab0d1d81ba7453d49bbc16250	   refs/tags/junio-gpg-pub
	   $ git ls-remote http://www.kernel.org/pub/scm/git/git.git master pu rc
	   5fe978a5381f1fbad26a80e682ddd2a401966740	   refs/heads/master
	   c781a84b5204fb294c9ccc79f8b3baceeb32c061	   refs/heads/pu
	   b1d096f2926c4e37c9c0b6a7bf2119bedaa277cb	   refs/heads/rc
	   $ echo http://www.kernel.org/pub/scm/git/git.git >.git/branches/public
	   $ git ls-remote --tags public v*
	   d6602ec5194c87b0fc87103ca4d67251c76f233a	   refs/tags/v0.99
	   f25a265a342aed6041ab0cc484224d9ca54b6f41	   refs/tags/v0.99.1
	   c5db5456ae3b0873fc659c19fafdde22313cc441	   refs/tags/v0.99.2
	   7ceca275d047c90c0c7d5afb13ab97efdf51bd6e	   refs/tags/v0.99.3

GIT

       Part of the git(1) suite

Git 1.7.10.4							    11/24/2012							  GIT-LS-REMOTE(1)