9 More Discussions You Might Find Interesting
1. Ubuntu
Hi,
I copied the key of rsa.pub to authorized_keys using the below command
cat /root/.ssh/id_rsa.pub >> /root/.ssh/authorized_keys
By mistake i have executed another command
view cat /root/.ssh/id_rsa.pub >> /root/.ssh/authorized_keys
so now additional keys are copied.so please help me... (3 Replies)
Discussion started by: SA_Palani
3 Replies
2. Red Hat
Hi All,
I am trying to revert a snapshot and I am getting the below error message in my KVM setup (RHEL6.5). Reverting to a snapshot is failing.
I used the below command to create the snapshot.
Below is my snapshot list:
virsh snapshot-list TestImg –tree
... (0 Replies)
Discussion started by: kalpeer
0 Replies
3. UNIX for Dummies Questions & Answers
I have given as:
PS1="Karthick>" in linux.
Now the prompt changed as:
Karthick>
Now I need to get back the default prompt .
How to achieve this?
Thanks in advance (13 Replies)
Discussion started by: karthick nath
13 Replies
4. Emergency UNIX and Linux Support
I know, its stupid..
MYSQL on CENTOS 5 using WHM
Imported a lot of users/posts from old forum to new forum, but my backup was lost.
Can I somehow simply remove all mysql table changes for the last 3 hours, returning to pre-import status.
---------- Post updated at 03:44 AM ----------... (6 Replies)
Discussion started by: lawstudent
6 Replies
5. UNIX for Advanced & Expert Users
Hi,
I have deleted a file and commited in CVS.
So, is there any CVS command to revert back that deleted file with existing log messages.
--Thanks in advance
Madhu (1 Reply)
Discussion started by: madhuti
1 Replies
6. HP-UX
All,
I have inherited some software that is running on HP-HX 11.11. The software ofers a GUI login and the user passwords can be either internal to the software, user defined or based on the matching unix account. The problem I have is that the server has been converted to 'trusted' years... (7 Replies)
Discussion started by: rbatte1
7 Replies
7. Linux
Long story short, there was some sort of corruption with my ide and the script I was working on has been over written with nothing (the file is blank now). The IDE doesn't store a back up from what I know (I'm using notepadd++ in wine lol I know I know I'm addictted to the nppftp sidebar and geany... (1 Reply)
Discussion started by: noPermissions
1 Replies
8. Emergency UNIX and Linux Support
Instead of importing a project/folder as
svn import vlsms/ file:///home/repo/vlsms -m "Initial Upload"
I did
svn import vlsms/ file:///home/repo -m "Initial Upload"
How to undo this import (in a clean way,without trace?)
---------- Post updated at 03:10 AM ---------- Previous update was at... (0 Replies)
Discussion started by: johnbach
0 Replies
9. Solaris
hi i have created a pool using zpool command for my /dev/dsk/c1d0s3 disk.
The poolname is qwertyuiopasdfghjklmnbvcxzzxcvbnmasdfghjklqwertyuiopoiuytrewqasdfghjklkjhgfdsazxcvbnmmnbnbcxczxzassd
ddddvfhfghgjjgjhgkhkljfjlhohihiuyuioyguioyguiowyuiogwyuigwrigywuigyguiyuiogyugiyguioyuyguiowygiuygui... (1 Reply)
Discussion started by: SankarV
1 Replies
GIT-REVERT(1) Git Manual GIT-REVERT(1)
NAME
git-revert - Revert some existing commits
SYNOPSIS
git revert [--[no-]edit] [-n] [-m parent-number] [-s] [-S[<keyid>]] <commit>...
git revert --continue
git revert --quit
git revert --abort
DESCRIPTION
Given one or more existing commits, revert the changes that the related patches introduce, and record some new commits that record them.
This requires your working tree to be clean (no modifications from the HEAD commit).
Note: git revert is used to record some new commits to reverse the effect of some earlier commits (often only 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>...
Commits to revert. For a more complete list of ways to spell commit names, see gitrevisions(7). Sets of commits can also be given but
no traversal is done by default, see git-rev-list(1) and its --no-walk option.
-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 some commits with commit log messages stating which commits were reverted. This flag applies
the changes necessary to revert the named commits to your working tree and the index, but does not make the commits. 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[<keyid>], --gpg-sign[=<keyid>]
GPG-sign commits. The keyid argument is optional and defaults to the committer identity; if specified, it must be stuck to the option
without a space.
-s, --signoff
Add Signed-off-by line at the end of the commit message. See the signoff option in git-commit(1) for more information.
--strategy=<strategy>
Use the given merge strategy. Should only be used once. See the MERGE STRATEGIES section in git-merge(1) for details.
-X<option>, --strategy-option=<option>
Pass the merge strategy-specific option through to the merge strategy. See git-merge(1) for details.
SEQUENCER SUBCOMMANDS
--continue
Continue the operation in progress using the information in .git/sequencer. Can be used to continue after resolving conflicts in a
failed cherry-pick or revert.
--quit
Forget about the current operation in progress. Can be used to clear the sequencer state after a failed cherry-pick or revert.
--abort
Cancel the operation and return to the pre-sequence state.
EXAMPLES
git revert HEAD~3
Revert the changes specified by the fourth last commit in HEAD and create a new commit with the reverted changes.
git revert -n master~5..master~2
Revert the changes done by commits from the fifth last commit in master (included) to the third last commit in master (included), but
do not create any commit with the reverted changes. The revert only modifies the working tree and the index.
SEE ALSO
git-cherry-pick(1)
GIT
Part of the git(1) suite
NOTES
1. revert-a-faulty-merge How-To
file:///usr/share/doc/git/html/howto/revert-a-faulty-merge.html
Git 2.17.1 10/05/2018 GIT-REVERT(1)