From: Michal Marek <mmarek@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Joe Perches <joe@perches.com>,
linux-next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
users@kernel.org
Subject: Re: RFC: Removing old tags, reducing the git size of -next.
Date: Wed, 09 Mar 2011 10:41:32 +0100 [thread overview]
Message-ID: <4D774B4C.7030409@suse.cz> (raw)
In-Reply-To: <20110309032332.da40748b.sfr@canb.auug.org.au>
On 8.3.2011 17:23, Stephen Rothwell wrote:
> Hi Michal,
>
> On Tue, 08 Mar 2011 16:29:29 +0100 Michal Marek <mmarek@suse.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
prev parent reply other threads:[~2011-03-09 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1299039746.4208.28.camel@Joe-Laptop>
2011-03-02 5:54 ` RFC: Removing old tags, reducing the git size of -next Stephen Rothwell
2011-03-08 15:29 ` Michal Marek
2011-03-08 16:23 ` Stephen Rothwell
2011-03-09 9:41 ` Michal Marek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D774B4C.7030409@suse.cz \
--to=mmarek@suse.cz \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=users@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox