7 More Discussions You Might Find Interesting
1. HP-UX
OS: HP-UX B.11.31 U ia64
shell : /sbin/sh
Messages like "debug3: Wrote 48 bytes for a total of 15837" are thrown in my terminal after each key stroke. If I try to type a command such message appears after each character I type. If I simply press enter messages like below appear.
... (1 Reply)
Discussion started by: black_fender
1 Replies
2. Programming
(I have long gap to communicate with C++ and do not recall if I have used 'try-catch' at all; so, looking for advice...)
I am trying to understand what the benefits of using that C++ error handling style compare to regular C-style 'if-then'?
Still in the try{} block need to do some 'if()' to... (4 Replies)
Discussion started by: alex_5161
4 Replies
3. Shell Programming and Scripting
Hi,
I have a requirement like i have to search a script and find names that conatins more than two dots, if so then throw error.
For ex: a1.b1.comname here i have to find comname and check two dots. it will not throw error
a1.b1.c1.comname here it contains more than 2dots it will throw... (3 Replies)
Discussion started by: swagat123
3 Replies
4. Shell Programming and Scripting
Hi I have script that is developed to serch for 30 days old Directory & Files and then remove them ...
when i run it successfully removes the Directory & files & but it throw errors on the screen
..
..
+ find . -type f -mtime +30 -exec rm -f {} ;
+ exit
please help me ??
I... (0 Replies)
Discussion started by: Beginner123
0 Replies
5. UNIX for Dummies Questions & Answers
I want to count the number of lines in a file and store it in a variable if this count is zero i hv to throw an error ...is this syntax correct , but i am not getting the desired result
I am not using -s option here as i am concerned about record count not the size
#!/bin/ksh
set $count1... (4 Replies)
Discussion started by: mavesum
4 Replies
6. Shell Programming and Scripting
hi all,
in ksh, is there a way to throw a generic error message. i have lots of commands in my script and i didnt want to put
if ; then
doStuff();
else
print "an error occured, please run script again";
fi
around all the commands used. is there a way detect a command has... (1 Reply)
Discussion started by: cesarNZ
1 Replies
7. Shell Programming and Scripting
hello all
i have string that i need to parse something list that :
<form name="CustomerStatus" action="<% env.GetURI %>" method="post"<$if(blah)%> name="<% env.get("StatusList") %>" ><% hello %><input type="hidden" name="<% env.get("Operation") %>" value="">
now im selecting the the string... (6 Replies)
Discussion started by: umen
6 Replies
LEARN ABOUT MOJAVE
git-shortlog
GIT-SHORTLOG(1) Git Manual GIT-SHORTLOG(1)
NAME
git-shortlog - Summarize 'git log' output
SYNOPSIS
git log --pretty=short | git shortlog [<options>]
git shortlog [<options>] [<revision range>] [[--] <path>...]
DESCRIPTION
Summarizes git log output in a format suitable for inclusion in release announcements. Each commit will be grouped by author and title.
Additionally, "[PATCH]" will be stripped from the commit description.
If no revisions are passed on the command line and either standard input is not a terminal or there is no current branch, git shortlog will
output a summary of the log read from standard input, without reference to the current repository.
OPTIONS
-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.
--format[=<format>]
Instead of the commit subject, use some other information to describe each commit. <format> can be any string accepted by the --format
option of git log, such as * [%h] %s. (See the "PRETTY FORMATS" section of git-log(1).)
Each pretty-printed commit will be rewrapped before it is shown.
-c, --committer
Collect and show committer identities instead of authors.
-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.
If width is 0 (zero) then indent the lines of the output without wrapping them.
<revision range>
Show only commits in the specified revision range. When no <revision range> is specified, it defaults to HEAD (i.e. the whole history
leading to the current commit). origin..HEAD specifies all the commits reachable from the current commit (i.e. HEAD), but not from
origin. For a complete list of ways to spell <revision range>, see the "Specifying Ranges" section of gitrevisions(7).
[--] <path>...
Consider only commits that are enough to explain how the files that match the specified paths came to be.
Paths may need to be prefixed with "-- " to separate them from options or the revision range, when confusion arises.
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 or mailmap.blob
configuration options, 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:
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)>
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:
Jane Doe <jane@desktop.(none)>
Joe R. Developer <joe@example.com>
Note how there is no need for an entry for <jane@laptop.(none)>, because the real name of that author is already correct.
Example 2: Your repository contains commits from the following authors:
nick1 <bugs@company.xx>
nick2 <bugs@company.xx>
nick2 <nick2@company.xx>
santa <me@company.xx>
claus <me@company.xx>
CTO <cto@coompany.xx>
Then you might want a .mailmap file that looks like:
<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>
Use hash # for comments that are either on their own line, or after the email address.
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-SHORTLOG(1)