09-29-2017
I got the RHCE for RHEL 6 a few years ago and remember it being full of useless guff, such as configuring SAMBA users as well as users for other services, as well as iSCSI, etc. that you mention, none of which I've ever used (so, of course, have forgotten - it's hard to commit such rubbish to memory!).
And, while I've studied for the RHEL 7 RHCE haven't taken the exam yet, because it's expensive and full of much the same useless stuff.
It's probably good to learn a lot of the other, more useful stuff, just for your own knowledge, but I really don't think it's worth the effort, time or money to do all that's necessary for the exam (unless someone else is paying for it).
Probably looks good on the CV, but that's about it, IMO.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Are there any nationally recognized UNIX certifications, similar to A+., for basic unix and system admin skills?
thanks (1 Reply)
Discussion started by: pacsman
1 Replies
2. What is on Your Mind?
Hi all,
I'm new to this forum also to unix, but eager to learn unix.
Can any one gimme the certifications/exams available to validate our unix strengths. (7 Replies)
Discussion started by: sarang
7 Replies
3. UNIX for Dummies Questions & Answers
Hello I am a newbie i learnt Shell programming and Unix Internals.Well plz advice me what certifications i shud do as i have free time and want to utilize my time :) (1 Reply)
Discussion started by: strawberry
1 Replies
4. Shell Programming and Scripting
Guys,
I just want information abt certifications available for unix. If they exist can anyone give some info them. Making clear I am pointing to developer level exams, not admin side.
Thanks,
Sharif.S (0 Replies)
Discussion started by: sharifhere
0 Replies
5. AIX
Hi ,
I want to know aix certifications,How to perepare for that ?How many number of papers are there? (12 Replies)
Discussion started by: manoj.solaris
12 Replies
6. Shell Programming and Scripting
Hi All,
Can anybody let me know if there is any Unix certification course which will provide basically programming in Unix. (4 Replies)
Discussion started by: darshakraut
4 Replies
7. What is on Your Mind?
hi there :)
I will study the Linux LPI certification in a few months
What do u think about it?
Is this certification good enough to work with solaris too actually? I´m not sure because i think is more oriented to linux, and solaris as far as i know, is based on UNix.
What else can i... (3 Replies)
Discussion started by: andriusman
3 Replies
8. HP-UX
Hi,
I am planning to get certified on HP-UX.
I googled about HPUX Certifications. I understand that I need to pass on exam HP0-A01 but I find many references to HP0-095.
I bought this book:
HP-UX: HP Certification Systems Administrator, Exam HP0-A01 - Training Guide and Administrator's... (16 Replies)
Discussion started by: psicopunk
16 Replies
9. What is on Your Mind?
Hi ,
I am working in Perl/Shell Script for past 3 years.I am planning to learn and switch my Career as Linux Admin.So Please suggest some certifications to learn about it.Do we have separate sub categories/area of specifications in Linux Admin ? Like Virtualization ,Vmware,storage. ... (0 Replies)
Discussion started by: Ajaytts123
0 Replies
LEARN ABOUT MOJAVE
git-cherry
GIT-CHERRY(1) Git Manual GIT-CHERRY(1)
NAME
git-cherry - Find commits yet to be applied to upstream
SYNOPSIS
git cherry [-v] [<upstream> [<head> [<limit>]]]
DESCRIPTION
Determine whether there are commits in <head>..<upstream> that are equivalent to those in the range <limit>..<head>.
The equivalence test is based on the diff, after removing whitespace and line numbers. git-cherry therefore detects when commits have been
"copied" by means of git-cherry-pick(1), git-am(1) or git-rebase(1).
Outputs the SHA1 of every commit in <limit>..<head>, prefixed with - for commits that have an equivalent in <upstream>, and + for commits
that do not.
OPTIONS
-v
Show the commit subjects next to the SHA1s.
<upstream>
Upstream branch to search for equivalent commits. Defaults to the upstream branch of HEAD.
<head>
Working branch; defaults to HEAD.
<limit>
Do not report commits up to (and including) limit.
EXAMPLES
Patch workflows
git-cherry is frequently used in patch-based workflows (see gitworkflows(7)) to determine if a series of patches has been applied by the
upstream maintainer. In such a workflow you might create and send a topic branch like this:
$ git checkout -b topic origin/master
# work and create some commits
$ git format-patch origin/master
$ git send-email ... 00*
Later, you can see whether your changes have been applied by saying (still on topic):
$ git fetch # update your notion of origin/master
$ git cherry -v
Concrete example
In a situation where topic consisted of three commits, and the maintainer applied two of them, the situation might look like:
$ git log --graph --oneline --decorate --boundary origin/master...topic
* 7654321 (origin/master) upstream tip commit
[... snip some other commits ...]
* cccc111 cherry-pick of C
* aaaa111 cherry-pick of A
[... snip a lot more that has happened ...]
| * cccc000 (topic) commit C
| * bbbb000 commit B
| * aaaa000 commit A
|/
o 1234567 branch point
In such cases, git-cherry shows a concise summary of what has yet to be applied:
$ git cherry origin/master topic
- cccc000... commit C
+ bbbb000... commit B
- aaaa000... commit A
Here, we see that the commits A and C (marked with -) can be dropped from your topic branch when you rebase it on top of origin/master,
while the commit B (marked with +) still needs to be kept so that it will be sent to be applied to origin/master.
Using a limit
The optional <limit> is useful in cases where your topic is based on other work that is not in upstream. Expanding on the previous example,
this might look like:
$ git log --graph --oneline --decorate --boundary origin/master...topic
* 7654321 (origin/master) upstream tip commit
[... snip some other commits ...]
* cccc111 cherry-pick of C
* aaaa111 cherry-pick of A
[... snip a lot more that has happened ...]
| * cccc000 (topic) commit C
| * bbbb000 commit B
| * aaaa000 commit A
| * 0000fff (base) unpublished stuff F
[... snip ...]
| * 0000aaa unpublished stuff A
|/
o 1234567 merge-base between upstream and topic
By specifying base as the limit, you can avoid listing commits between base and topic:
$ git cherry origin/master topic base
- cccc000... commit C
+ bbbb000... commit B
- aaaa000... commit A
SEE ALSO
git-patch-id(1)
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-CHERRY(1)