06-18-2010
that did it I had to remove the other csm.xx 1.7.0.0 packages, then re-apply TL5 then it reverted back to TL6. Thanks.
10 More Discussions You Might Find Interesting
1. AIX
Hi All,
Would like to know what files or file sets are referred when the 'oslevel -s' command is executed, and the mechanism that it uses to give us the output regarding the ML and the SP level of the machine. Any help would be highly appreciated.
Thanks in advance!
Regards
Digiwolf123 (3 Replies)
Discussion started by: digiwolf123
3 Replies
2. AIX
Hi ,
Can you suggest me how to back to back printing in UNIX? Is there any way?
Kindly advise.
Regards
Vijaya Amirtha Raj (3 Replies)
Discussion started by: amirthraj_12
3 Replies
3. IP Networking
Hi every body,
Is it possible to connect two servers Back-to-Back (Point-to-Point) using HBA adapters & using Fiber.
Note it is direct connection & there is no switches between the servers.
I'm concern about using HBA adapters, it is possible or not.
Thanks in advance. :) (3 Replies)
Discussion started by: aldowsary
3 Replies
4. Solaris
what are the major Difference Between run level & init level (2 Replies)
Discussion started by: rajaramrnb
2 Replies
5. AIX
I just upgraded my system from 53tl9 to 53tl10 and it is still showing 53tl9 (5300-09). When I run oslevel -rl 5300-10 or oslevel -r -l 5300-10 I get the following error "Error: Recommended Maintenance level 5300-11 is invalid or unknown." How do I determine what files are missing from the... (3 Replies)
Discussion started by: daveisme
3 Replies
6. Shell Programming and Scripting
#!/bin/sh
##########################################################################################################
#This script is being used for AOK application for cleaning up the .out files and zip it under logs directory.
# IBM
# Created
#For pdocap201/pdoca202 .out files for AOK
#1.... (0 Replies)
Discussion started by: mridul10_crj
0 Replies
7. AIX
Hi,
is it possible to roll back currently updated Technology level ? what are steps required?
Regards,
Manoj (2 Replies)
Discussion started by: manoj.solaris
2 Replies
8. Shell Programming and Scripting
Hi Agian
Sorry for all these questions...:
Last one for a whie, I promise
This is an example of a menu script I am using. It works OK...when I get to the 2nd menu level, if the command is issued or canceled, I would like to go back to the first menu (# MAIN SECTION)
This is NOT the... (7 Replies)
Discussion started by: olearydc
7 Replies
9. Red Hat
We have a RHEL 5.8 server at the production level and we have a Java application on this server. I know of the SSL certificate generation at the OS (RHEL) level but it is implemented on the Java application by our development team using the Java keytool. My doubt is that is the SSL generation can... (3 Replies)
Discussion started by: RHCE
3 Replies
10. Shell Programming and Scripting
I am parsing a log with this format:
06:36:12.230 details here
06:36:12.250 details here
06:36:12.260 details here
continuation here
06:36:12.360 details here
As you can see, some detail info contains one or more "\n" and it breaks my line-oriented parsing.
I need to get those... (3 Replies)
Discussion started by: migurus
3 Replies
LEARN ABOUT SUSE
git-revert
GIT-REVERT(1) Git Manual GIT-REVERT(1)
NAME
git-revert - Revert an existing commit
SYNOPSIS
git revert [--edit | --no-edit] [-n] [-m parent-number] [-s] <commit>
DESCRIPTION
Given one existing commit, revert the change the patch introduces, and record a new commit that records it. This requires your working tree
to be clean (no modifications from the HEAD commit).
Note: git revert is used to record a new commit to reverse the effect of an earlier commit (often a faulty one). If you want to throw away
all uncommitted changes in your working directory, you should see git-reset(1), particularly the --hard option. If you want to extract
specific files as they were in another commit, you should see git-checkout(1), specifically the git checkout <commit> -- <filename> syntax.
Take care with these alternatives as both will discard uncommitted changes in your working directory.
OPTIONS
<commit>
Commit to revert. For a more complete list of ways to spell commit names, see "SPECIFYING REVISIONS" section in git-rev-parse(1).
-e, --edit
With this option, git revert will let you edit the commit message prior to committing the revert. This is the default if you run the
command from a terminal.
-m parent-number, --mainline parent-number
Usually you cannot revert a merge because you do not know which side of the merge should be considered the mainline. This option
specifies the parent number (starting from 1) of the mainline and allows revert to reverse the change relative to the specified parent.
Reverting a merge commit declares that you will never want the tree changes brought in by the merge. As a result, later merges will
only bring in tree changes introduced by commits that are not ancestors of the previously reverted merge. This may or may not be what
you want.
See the revert-a-faulty-merge How-To[1] for more details.
--no-edit
With this option, git revert will not start the commit message editor.
-n, --no-commit
Usually the command automatically creates a commit with a commit log message stating which commit was reverted. This flag applies the
change necessary to revert the named commit to your working tree and the index, but does not make the commit. In addition, when this
option is used, your index does not have to match the HEAD commit. The revert is done against the beginning state of your index.
This is useful when reverting more than one commits' effect to your index in a row.
-s, --signoff
Add Signed-off-by line at the end of the commit message.
AUTHOR
Written by Junio C Hamano <gitster@pobox.com[2]>
DOCUMENTATION
Documentation by Junio C Hamano and the git-list <git@vger.kernel.org[3]>.
GIT
Part of the git(1) suite
NOTES
1. revert-a-faulty-merge How-To
file:///usr/share/doc/git-doc/howto/revert-a-faulty-merge.txt
2. gitster@pobox.com
mailto:gitster@pobox.com
3. git@vger.kernel.org
mailto:git@vger.kernel.org
Git 1.7.1 07/05/2010 GIT-REVERT(1)