10 More Discussions You Might Find Interesting
1. Solaris
Hi all,
I have read about sendmail running as 2 separate process.
1 as a MSP, and the other as the real daemon or MTA.
In my current configuration,
the sendmail-client is disabled.
Both submit.cf and sendmail.cf are left as default untouch
I do not specified any mailhost... (3 Replies)
Discussion started by: javanoob
3 Replies
2. AIX
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
3. UNIX for Advanced & Expert Users
I am running SCO 5.0.6 and using sendmail 8.11.0 and having issues with smtp authentication. When trying to send mail the following message will kick back.
(reason: 530 5.7.1 Authentication required)
530 5.7.1 Authentication required
Not sure what needs to be tweeked in sendmail.cf but I... (1 Reply)
Discussion started by: ziggy6
1 Replies
4. AIX
I am attempting this for the first time having in the past used a DVD migrate. Unfortunately in this instance I do not have this luxury. The migration starts correctly and creates the alt_inst disk and them proceeds to create the filesystems and exports them. First failure was the filesystem... (3 Replies)
Discussion started by: johnf
3 Replies
5. UNIX for Dummies Questions & Answers
Dear Admin,
I am new to unix platform,please i need you to tell me and send me useful tools and advice on how to migrate an oracle DB release2 to a unix platform.
your urgent responce would be appreciated.
Regards,
Adejuwon Odugbesi. (1 Reply)
Discussion started by: adejuwon
1 Replies
6. Solaris
Hi, it is necessary to make the migration of Solaris 5.8 for Solaris 10, would like to know which the best form to execute this task, if to be able to say me where I can arrange some manual that helps me to make this task. Thanks :o (2 Replies)
Discussion started by: bruno_a_correia
2 Replies
7. Shell Programming and Scripting
Hi all
Can any one guide me what changes may occur with this OS version migration. If you could give some links, that would be helpful too.
Regards,
Ranj (2 Replies)
Discussion started by: ranj@chn
2 Replies
8. UNIX for Advanced & Expert Users
Hi all,
Would appreciate advise on my situation.
Currently server A is in production. Server A takes in data from Server X, does some processing and send to server Y. We are going to develop a different system in server B, something like an enhanced version of A. Server A will be retired once... (2 Replies)
Discussion started by: new2ss
2 Replies
9. UNIX for Advanced & Expert Users
hi,
is there any tool that i can use to update my scripts (SH scripts)
form Unix to linux.
please mention any useful websites.
thanx in advance (2 Replies)
Discussion started by: omran
2 Replies
10. UNIX for Dummies Questions & Answers
Is it possible to migrate a UNIX program and use it in a NetWare or Windows 2000 network? I have a client that must have one of those two operating systems for the new program that they want. However, they've been using an older UNIX program for about 7 years and they want to be able to refer to... (7 Replies)
Discussion started by: refram
7 Replies
GIT-SHORTLOG(1) Git Manual GIT-SHORTLOG(1)
NAME
git-shortlog - Summarize 'git log' output
SYNOPSIS
git log --pretty=short | git shortlog [-h] [-n] [-s] [-e] [-w]
git shortlog [-n|--numbered] [-s|--summary] [-e|--email] [-w[<width>[,<indent1>[,<indent2>]]]] [<committish>...]
DESCRIPTION
Summarizes git log output in a format suitable for inclusion in release announcements. Each commit will be grouped by author and the first
line of the commit message will be shown.
Additionally, "[PATCH]" will be stripped from the commit description.
OPTIONS
-h, --help
Print a short usage message and exit.
-n, --numbered
Sort output according to the number of commits per author instead of author alphabetic order.
-s, --summary
Suppress commit description and provide a commit count summary only.
-e, --email
Show the email address of each author.
-w[<width>[,<indent1>[,<indent2>]]]
Linewrap the output by wrapping each line at width. The first line of each entry is indented by indent1 spaces, and the second and
subsequent lines are indented by indent2 spaces. width, indent1, and indent2 default to 76, 6 and 9 respectively.
MAPPING AUTHORS
The .mailmap feature is used to coalesce together commits by the same person in the shortlog, where their name and/or email address was
spelled differently.
If the file .mailmap exists at the toplevel of the repository, or at the location pointed to by the mailmap.file configuration option, it
is used to map author and committer names and email addresses to canonical real names and email addresses.
In the simple form, each line in the file consists of the canonical real name of an author, whitespace, and an email address used in the
commit (enclosed by < and >) to map to the name. For example:
Proper Name <commit@email.xx>
The more complex forms are:
<proper@email.xx> <commit@email.xx>
which allows mailmap to replace only the email part of a commit, and:
Proper Name <proper@email.xx> <commit@email.xx>
which allows mailmap to replace both the name and the email of a commit matching the specified commit email address, and:
Proper Name <proper@email.xx> Commit Name <commit@email.xx>
which allows mailmap to replace both the name and the email of a commit matching both the specified commit name and email address.
Example 1: Your history contains commits by two authors, Jane and Joe, whose names appear in the repository under several forms:
.ft C
Joe Developer <joe@example.com>
Joe R. Developer <joe@example.com>
Jane Doe <jane@example.com>
Jane Doe <jane@laptop.(none)>
Jane D. <jane@desktop.(none)>
.ft
Now suppose that Joe wants his middle name initial used, and Jane prefers her family name fully spelled out. A proper .mailmap file would
look like:
.ft C
Jane Doe <jane@desktop.(none)>
Joe R. Developer <joe@example.com>
.ft
Note how there is no need for an entry for <jane@laptop[1].(none)>, because the real name of that author is already correct.
Example 2: Your repository contains commits from the following authors:
.ft C
nick1 <bugs@company.xx>
nick2 <bugs@company.xx>
nick2 <nick2@company.xx>
santa <me@company.xx>
claus <me@company.xx>
CTO <cto@coompany.xx>
.ft
Then you might want a .mailmap file that looks like:
.ft C
<cto@company.xx> <cto@coompany.xx>
Some Dude <some@dude.xx> nick1 <bugs@company.xx>
Other Author <other@author.xx> nick2 <bugs@company.xx>
Other Author <other@author.xx> <nick2@company.xx>
Santa Claus <santa.claus@northpole.xx> <me@company.xx>
.ft
Use hash # for comments that are either on their own line, or after the email address.
AUTHOR
Written by Jeff Garzik <jgarzik@pobox.com[2]>
DOCUMENTATION
Documentation by Junio C Hamano.
GIT
Part of the git(1) suite
NOTES
1. jane@laptop
mailto:jane@laptop
2. jgarzik@pobox.com
mailto:jgarzik@pobox.com
Git 1.7.1 07/05/2010 GIT-SHORTLOG(1)