Sponsored Content
The Lounge What is on Your Mind? Your Favorite Tech Support Web Sites and Why? Post 303022213 by Neo on Monday 27th of August 2018 10:13:32 PM
Old 08-27-2018
Your Favorite Tech Support Web Sites and Why?

Where do you go to participate in technical discussions besides UNIX.COM and why?

Personally, I do not really participate in other forums and discussion boards, but I do ask questions from time to time on Stack sites. The problem I have with Stack is that my questions are never answered on any topic; so perhaps they are not the standard, beginner questions that we often see. Or, perhaps I not good at asking questions, haha.

This means for me, I normally get my tech answers from a Google search or watching a tutorial video; because I have very bad luck asking questions and getting answers in forums and other discussion sites.

I also find Stack sites to be really restrictive, because these sites do not really promote back and forth discussions, but they are rather "post a question and vote up the best answer" sites. So, when I try to post on any of these kind of sites, I cannot get any sense of community; but that's me I guess; maybe others have better experiences?

I do like the fact that the Stack sites are not forum based but taxonomy (tag) based, so there is no need to post in a particular forum or designed area on the site; but just tag the post with one or more keywords and go.

Also, on the Stack sites, I have difficulty with code tags and other BB code tags; and sometimes I really struggle to get code posted. This means for me, I often get good information from Stack but only from a Google search referral, but rarely, to almost never, get my written questions answered.

How about about you?

Where are your favorite tech discussion hangouts and why?
 

5 More Discussions You Might Find Interesting

1. OS X (Apple)

Use UNIX to track web sites viewed?

I'm on OSX 10.4. I was wondering if you can use UNIX terminal to track what web sites have been viewed on this Mac... Thank you! (1 Reply)
Discussion started by: tracymanusa
1 Replies

2. UNIX for Dummies Questions & Answers

Generation file copying for tech support backup

Hi All, I've looked through the forum and haven't quite found what I'm looking to do. We're migrating our systems from a midrange to HP-UX, and I'm quite new to UNIX so I'm hoping that I can get pointed in the right direction. What I'm looking to do is save generations of files for... (12 Replies)
Discussion started by: sjohnson
12 Replies

3. Web Development

How do you make web sites?

:confused: I've read how on some websites but I still don't get it. I need specific details. I want to make a website for my photography. Please help!:D (3 Replies)
Discussion started by: animelibara123
3 Replies

4. Web Development

What is Your Favorite Web Browser?

OK, please vote on your favorite web browser and comment why! Only currently supported browers please! Thanks. PS: I am a big FireFox fan. FireFox add-ons rock! (61 Replies)
Discussion started by: Neo
61 Replies

5. Red Hat

Web sites

Hi, I can't view web portal in my intranet from linux RHE, and neither to web application. My network configuration /etc/sysconfig/network-scripts/fcfg-eth0 is ok, what is happen?, can you help me please. (2 Replies)
Discussion started by: xochitl
2 Replies
GIT-MAILINFO(1) 						    Git Manual							   GIT-MAILINFO(1)

NAME
git-mailinfo - Extracts patch and authorship from a single e-mail message SYNOPSIS
git mailinfo [-k|-b] [-u | --encoding=<encoding> | -n] [--[no-]scissors] <msg> <patch> DESCRIPTION
Reads a single e-mail message from the standard input, and writes the commit log message in <msg> file, and the patches in <patch> file. The author name, e-mail and e-mail subject are written out to the standard output to be used by git am to create a commit. It is usually not necessary to use this command directly. See git-am(1) instead. OPTIONS
-k Usually the program removes email cruft from the Subject: header line to extract the title line for the commit log message. This option prevents this munging, and is most useful when used to read back git format-patch -k output. Specifically, the following are removed until none of them remain: o Leading and trailing whitespace. o Leading Re:, re:, and :. o Leading bracketed strings (between [ and ], usually [PATCH]). Finally, runs of whitespace are normalized to a single ASCII space character. -b When -k is not in effect, all leading strings bracketed with [ and ] pairs are stripped. This option limits the stripping to only the pairs whose bracketed string contains the word "PATCH". -u The commit log message, author name and author email are taken from the e-mail, and after minimally decoding MIME transfer encoding, re-coded in the charset specified by i18n.commitencoding (defaulting to UTF-8) by transliterating them. This used to be optional but now it is the default. Note that the patch is always used as-is without charset conversion, even with this flag. --encoding=<encoding> Similar to -u. But when re-coding, the charset specified here is used instead of the one specified by i18n.commitencoding or UTF-8. -n Disable all charset re-coding of the metadata. -m, --message-id Copy the Message-ID header at the end of the commit message. This is useful in order to associate commits with mailing list discussions. --scissors Remove everything in body before a scissors line. A line that mainly consists of scissors (either ">8" or "8<") and perforation (dash "-") marks is called a scissors line, and is used to request the reader to cut the message at that line. If such a line appears in the body of the message before the patch, everything before it (including the scissors line itself) is ignored when this option is used. This is useful if you want to begin your message in a discussion thread with comments and suggestions on the message you are responding to, and to conclude it with a patch submission, separating the discussion and the beginning of the proposed commit log message with a scissors line. This can be enabled by default with the configuration option mailinfo.scissors. --no-scissors Ignore scissors lines. Useful for overriding mailinfo.scissors settings. <msg> The commit log message extracted from e-mail, usually except the title line which comes from e-mail Subject. <patch> The patch extracted from e-mail. GIT
Part of the git(1) suite Git 2.17.1 10/05/2018 GIT-MAILINFO(1)
All times are GMT -4. The time now is 06:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy