Sponsored Content
Full Discussion: Managing Geeks
The Lounge What is on Your Mind? Managing Geeks Post 302381443 by radoulov on Friday 18th of December 2009 07:16:23 AM
Old 12-18-2009
Very nice article,
thank you!
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

managing users

I need to setup several accounts on a solaris system. (passwd,shadow,group) My question is : How can I create a group which can access a machine, but only in certain directories? (4 Replies)
Discussion started by: SmartJuniorUnix
4 Replies

2. UNIX for Advanced & Expert Users

best solution for managing many nameservers

Hello, i was searching around for good solution for managing many nameservers to add the records on the slave servers and update them and if possible some web-based manegment for non-experianced customers. anyone has an idea where can i find such solution? (1 Reply)
Discussion started by: Bashar
1 Replies

3. UNIX for Advanced & Expert Users

Managing nodes???

Does anyone know something about this? I have no idea what it means and how to do it. but if anyone can give me and explanation and also point me to a website, i'd really appreciate it (5 Replies)
Discussion started by: TRUEST
5 Replies

4. Programming

error in managing linklist

I have used link list in my program to operate on set of values the operations that i am doing : add , delete from link list when i am deleting the intermidiate or last value it is not giving any error but when i am deleting the 1 st value then program hangs can anyone suggest me the reason (3 Replies)
Discussion started by: bhakti_2025
3 Replies

5. Solaris

Managing FileSystems on Solaris

Hello. I have got Solaris 10 8/07 on x86 installed successfully using CDs. While I had inserted 1st CD - I created 2 new filesystems also. But now after entering into Solaris - How do I manipulate sizes or created/delete filesystems by going to terminal? Thank you! (15 Replies)
Discussion started by: panchpan
15 Replies

6. Solaris

Problems managing user

I installed Solaris 10 in an old Dell computer given to me. The filesystem is ZFS (Default). The problem is that after logging in as root (first login) I wanted to add a user : n2jkw. I added the user at /export/home/n2jkw BTW, /export/home is where the 150G extra Hard Drive is mounted to.... (20 Replies)
Discussion started by: n2jkw
20 Replies

7. UNIX for Dummies Questions & Answers

expr help - managing strings

Hi guys, I need to use regular expressions in linux and I'm not quite experience in that field, maybe someone could give me some help with it. Basically, I need to take a text like this. A234321=http://www.google..... a normal URL But, I need to take the string starting at... (0 Replies)
Discussion started by: ocramas
0 Replies

8. Programming

Managing and using PTSes

Hello. I need to simulate a few serial links (doing a simulation of an application for a robot) and found socat which, at least with minicom, is working flawlessly. I would really like to make pts static: ie same numbers between reboots, and automatic (not me opening terminals and leaving... (2 Replies)
Discussion started by: erupter
2 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)
All times are GMT -4. The time now is 06:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy