# [ANNOUNCE] Git 1.7.7.3 3 messages from 2011-11-09 to 2011-11-12. Participants: Junio C Hamano, Eric Kom, Thiago Farina. Thread: https://gitlist.dev/t/28892 ## Junio C Hamano, 2011-11-09 01:15 Subject: [ANNOUNCE] Git 1.7.7.3 Message-ID: <7vsjlyw0y4.fsf@alter.siamese.dyndns.org> URL: https://gitlist.dev/e/7vsjlyw0y4.fsf%40alter.siamese.dyndns.org ``` The latest maintenance release Git 1.7.7.3 is available. The release tarballs are found at: http://code.google.com/p/git-core/downloads/list and their SHA-1 checksums are: 382ee40da74a1b4a1875820c0f0a35c9ccd750f8 git-1.7.7.3.tar.gz bc0f89cb04e562e4a6d3b936382dbc8f593d861f git-htmldocs-1.7.7.3.tar.gz cf1b0d35e2d242bc4cffce3b2bf5b3e32857b395 git-manpages-1.7.7.3.tar.gz Also the following public repositories all have a copy of the v1.7.7.3 tag and the maint branch that the tag points at: url = git://repo.or.cz/alt-git.git url = https://code.google.com/p/git-core/ url = git://git.sourceforge.jp/gitroot/git-core/git.git url = git://git-core.git.sourceforge.net/gitroot/git-core/git-core url = https://github.com/gitster/git ---------------------------------------------------------------- Changes since v1.7.7.2 are as follows: Dan McGee (4): pack-objects: mark add_to_write_order() as inline pack-objects: use unsigned int for counter and offset values pack-objects: rewrite add_descendants_to_write_order() iteratively pack-objects: don't traverse objects unnecessarily Jeff King (1): docs: don't mention --quiet or --exit-code in git-log(1) Julien Muchembled (1): gitweb: fix regression when filtering out forks Junio C Hamano (3): branch -m/-M: remove undocumented RENAMED-REF docs: Update install-doc-quick Git 1.7.7.3 ``` ## Eric Kom, 2011-11-11 05:48 Subject: Update Linux kernel branch source from GIT Message-ID: <4EBCB737.4090100@kom.za.net> URL: https://gitlist.dev/e/4EBCB737.4090100%40kom.za.net In-Reply-To: <7vsjlyw0y4.fsf@alter.siamese.dyndns.org> ``` Good day, Am new on this list, and also compile the kernel linux from git after clone. since I don't use the tar kernel version, am use to clone a new kernel branch instead to update it via patch. Please can you explain to me how to make a patch after clone it? This is my clone command: git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git linux-3.2 -- Your Truly Eric Kom 2 Hennie Van Till, White River, 1240 erickom@kom.za.net | erickom@namekom.co.za | erickom@erickom.co.za www.kom.za.net | www.kom.za.org | www.erickom.co.za Key fingerprint: 513E E91A C243 3020 8735 09BB 2DBC 5AD7 A9DA 1EF5 ``` ## Thiago Farina, 2011-11-12 20:59 Subject: Re: Update Linux kernel branch source from GIT Message-ID: URL: https://gitlist.dev/e/CACnwZYdFByS7pAgi5di8jDE%3DtYMvFQtxsTTiGqY9O0O3W04Dig%40mail.gmail.com In-Reply-To: <4EBCB737.4090100@kom.za.net> ``` On Fri, Nov 11, 2011 at 3:48 AM, Eric Kom wrote: > Good day, > > Am new on this list, and also compile the kernel linux from git after > clone. since I don't use the tar kernel version, am use to clone a new > kernel branch instead to update it via patch. > > Please can you explain to me how to make a patch after clone it? > To make a patch? I think you want something like this (uncompleted/untested offhand): $ git checkout -b my-patch origin/master # hack on some files $ git commit -a -s # edit commit message $ git format-patch $ git send-email Hugely these are the commands I'd use to make a change and send it out to LKML. ```