Sponsored Content
Top Forums Programming How to contribute Linux in Development? Post 302890133 by Corona688 on Tuesday 25th of February 2014 10:18:55 AM
Old 02-25-2014
Quote:
Originally Posted by tarun_nix
Hi Wisecracker,

What's the roadmap to be a developer for Linux on Kernel/patch/update.

I heard one has to complete Linux Architecture Certs to be one.. for above.
If you submit a working and useful kernel patch/update, they are likely to take it. Linux kernel hacking is an open-source venture.

This also means there isn't a big "Linux Corporation" that will hire you to do kernel patches/updates, because Linux is an open-source venture.
 

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

wanna contribute to gnu

I want to contribute to any project that currently going on in the gnu. What is the procedure. (1 Reply)
Discussion started by: yogesh_powar
1 Replies

2. What is on Your Mind?

Want to contribute to unix opensource projects.

Hello , I am C++, Objective C , Qt ,developer on Mac OS X, iOS having around 4+ years of experience. I never got a chance to work on System Level programming. But I am very much interested in it. I don't want to do UI programming any more but I am doing just because of my current job profile.... (2 Replies)
Discussion started by: want2bcomecoder
2 Replies
GIT-PATCH-ID(1) 						    Git Manual							   GIT-PATCH-ID(1)

NAME
git-patch-id - Compute unique ID for a patch SYNOPSIS
git patch-id < <patch> DESCRIPTION
A "patch ID" is nothing but a SHA1 of the diff associated with a patch, with whitespace and line numbers ignored. As such, it's "reasonably stable", but at the same time also reasonably unique, i.e., two patches that have the same "patch ID" are almost guaranteed to be the same thing. IOW, you can use this thing to look for likely duplicate commits. When dealing with git diff-tree output, it takes advantage of the fact that the patch is prefixed with the object name of the commit, and outputs two 40-byte hexadecimal strings. The first string is the patch ID, and the second string is the commit ID. This can be used to make a mapping from patch ID to commit ID. OPTIONS
<patch> The diff to create the ID of. AUTHOR
Written by Linus Torvalds <torvalds@osdl.org[1]> DOCUMENTATION
Documentation by Junio C Hamano and the git-list <git@vger.kernel.org[2]>. GIT
Part of the git(1) suite NOTES
1. torvalds@osdl.org mailto:torvalds@osdl.org 2. git@vger.kernel.org mailto:git@vger.kernel.org Git 1.7.1 07/05/2010 GIT-PATCH-ID(1)
All times are GMT -4. The time now is 04:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy