Sponsored Content
Full Discussion: Code Tags
Contact Us Post Here to Contact Site Administrators and Moderators Code Tags Post 302090689 by Perderabo on Wednesday 27th of September 2006 01:51:27 AM
Old 09-27-2006
Quote:
Originally Posted by Perderabo
"Failure to use code tags" is something that we can overcome.
What I meant by that is that we can indeed insert code tags. I have often inserted code tags. I always use preview though. Sometimes the code tags don't help.

So yes, moderators can insert code tags if they want to, but they can leave the post alone too. I certainly am not going to go through all of our threads inserting code tags on each thread that needs them. I still do not think that users should use the "report post" feature to report posts without code tags. We moderators do not need all that email.
 

We Also Found This Discussion For You

1. Post Here to Contact Site Administrators and Moderators

No code tags

Cound some kind moderator soul enforce the code tags rule on this thread - I'm tired of making fixes here and the OP doesn't obey the rules. (4 Replies)
Discussion started by: vgersh99
4 Replies
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. --get-url Expand the URL of the given remote repository taking into account any "url.<base>.insteadOf" config setting (See git-config(1)) and exit without talking to the remote. <repository> The "remote" repository to query. This parameter can be either a URL or the name of a remote (see the GIT URLS and REMOTES sections of git-fetch(1)). <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 $ git remote add korg http://www.kernel.org/pub/scm/git/git.git $ git ls-remote --tags korg 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.8.5.3 01/14/2014 GIT-LS-REMOTE(1)
All times are GMT -4. The time now is 05:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy