From: Franck <vagabon.xyz@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: git and tags...
Date: Wed, 9 Nov 2005 10:15:07 +0100 [thread overview]
Message-ID: <cda58cb80511090115h464b3e8fp@mail.gmail.com> (raw)
In-Reply-To: <20051108184521.GB2689@linux-mips.org>
2005/11/8, Ralf Baechle <ralf@linux-mips.org>:
> On Tue, Nov 08, 2005 at 06:25:06PM +0100, Franck wrote:
>
> > OK, so tags have been renamed into "linux-2.6.x". Why not using the
> > same mainline name convention (v2.6.x) ?
>
> The same reason that some people like blue and others prefer green ;-)
>
yet, mips branch follows mainline coding style...Actually it's just
more convenient to remember only one tag name convention. Anyways....
> > I have another question (which is the first one in my previous email),
> > how can I make my working tree a kernel version 2.6.9 for example ?
>
> git-read-tree $(cat .git/refs/tags/linux-2.6.9)
> git-checkout-index -f -a -u -q
>
thanks for that
> > And the last question related to mips git repository, why does kernel
> > v2.2, v2.4, v2.6 are in the same repository ? Why not seperate
> > different major version of the kernel in a seperate repository ?
>
> The extra space consumption for all these historic versions in a
> compressed git repository is extremly little.
>
hmm...still I get:
# du linux-mips.git/.git
263M
# du linux-mainline.git/.git
104M
Thanks
--
Franck
prev parent reply other threads:[~2005-11-09 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 10:49 git and tags Franck
2005-11-08 11:01 ` Ralf Baechle
2005-11-08 17:25 ` Franck
2005-11-08 18:45 ` Ralf Baechle
2005-11-08 21:31 ` Daniel Jacobowitz
2005-11-09 9:43 ` Franck
2005-11-09 9:15 ` Franck [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=cda58cb80511090115h464b3e8fp@mail.gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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