linux-kernel - Re: [PATCH 1/1] mct_u232: IOCTL implementation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LNX.2.00.1012262255080.20797@swampdragon.chaosbits.net>
Date:	Sun, 26 Dec 2010 23:03:15 +0100 (CET)
From:	Jesper Juhl <jj@...osbits.net>
To:	Tsozik <tsozik@...oo.com>
cc:	Randy Dunlap <rdunlap@...otime.net>, Greg KH <gregkh@...e.de>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] mct_u232: IOCTL implementation

On Sun, 26 Dec 2010, Tsozik wrote:

> Randy,
> 
> Greg referred to git as to place where change log comments are now 
> checked in. I googled it and found that one can also check out latest 
> kernel source code as opposed to tarball download. However, You're 
> right, looking at 
> http://kernelnewbies.org/UpstreamMerge/SubmittingPatches documentation I 
> don't see how one can use git to check in comments or code directly to 
> git repository,
> 

Only Linus can check code into the final official tree. But, you can use 
git to get a copy of the latest Linus tree (and many other trees run by 
various maintainers and others). Git is also useful for maintaining your 
own local branch with your changes.

The way it usually works is that you create a patch and send it off to 
some sub-system maintainer via email patch ('git diff' generated usually) 
or via email pull request for your personal repository. The sub-system 
maintainer then merges your patch with his tree and, at a later date, 
submits his tree (including your patch) to Linus.

Changelog comments are tracked with git. Once your patch is accepted it 
will eventually make its way to Linus' tree and your changelog comments in 
the patch mail (or git commit message - if you send a pull request) will 
eventually turn into a git commit message in the official tree. So there's 
no need to add changelog info in the files themselves.
Check http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=shortlog 
(or git log after cloning the tree) to see commit messages.

-- 
Jesper Juhl <jj@...osbits.net>            http://www.chaosbits.net/
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/