| 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
| ||
|
Message-ID: <4D774B4C.7030409@suse.cz> Date: Wed, 09 Mar 2011 10:41:32 +0100 From: Michal Marek <mmarek@...e.cz> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: Joe Perches <joe@...ches.com>, linux-next <linux-next@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>, users@...nel.org Subject: Re: RFC: Removing old tags, reducing the git size of -next. On 8.3.2011 17:23, Stephen Rothwell wrote: > Hi Michal, > > On Tue, 08 Mar 2011 16:29:29 +0100 Michal Marek <mmarek@...e.cz> wrote: >> >> FWIW, I use the following setup for linux-next: >> >> [remote "linux-next"] >> url = >> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git > > This should now be > git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > (its the same repository, just a more generic name). > >> fetch = +refs/heads/master:refs/heads/linux-next >> fetch = +refs/heads/stable:refs/remotes/linux-next/stable >> tagopt = --no-tags >> >> and fetch the next-* tags manually only when I need them. > > That should all continue to work. I probably quoted the wrong part of your email. I wanted to show that the full history of linux-next is not forced on anyone; git can be configured to only fetch the latest state and leave the previously fetched states to the garbage collector. Michal -- 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/
Powered by blists - more mailing lists