patches added to release/test trees

> That makes sense.  But why is the ia64 git tree missing
the Linus
> objects and tags in the first place?

"tags" is a bit ambiguous here, there are two
possible things that
you might be talking about when you say "tag"
w.r.t. a GIT tree.

1) A file in .git/refs/tags/ that contains the SHA1 of a git
object.

2) A git object of type "tag".

The files in .git/refs/tags refer to GIT tag objects. 
Usually a
tag object is a pointer to a commit object ... but they can
point
at anything (the v2.6.11 tag object points to a
"tree").

Things get more complex from here.  My kernel.org tree
contains none
of the .git/refs/tags files (because I "git
push" the heads of the
release/test branches up from my local tree, anf this won't
copy any
tags files up ... even though they are all in my local tree
from
my "git fetch linus" pulls from Linus).

The git tag objects actually are in my kernel.org tree!  But
only
because I share packfiles with Linus to reduce load on
kernel.org
mirroring system.

You don't get to see them though.  When you do a fetch/pull
from
my tree (using "git://" transfer method), git
will construct the
list of commit/tree/blob objects, build a packfile, and send
it to
you.  Any tag objects in my (really Linus') packfile will
just be
ignored.  If you used "rsync://", it would copy
the whole packfile.
Not sure what an http:// pull would do.


Is that as clear as mud now?

-Tony
-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html

"Luck, Tony" (on Fri, 23 Jun 2006 10:08:22
-0700) wrote:
>> That makes sense.  But why is the ia64 git tree
missing the Linus
>> objects and tags in the first place?
>
>"tags" is a bit ambiguous here, there are
two possible things that
>you might be talking about when you say
"tag" w.r.t. a GIT tree.
>
>1) A file in .git/refs/tags/ that contains the SHA1 of a
git object.

Them.

>2) A git object of type "tag".
>
>The files in .git/refs/tags refer to GIT tag objects. 
Usually a
>tag object is a pointer to a commit object ... but they
can point
>at anything (the v2.6.11 tag object points to a
"tree").
>
>Things get more complex from here.  My kernel.org tree
contains none
>of the .git/refs/tags files (because I "git
push" the heads of the
>release/test branches up from my local tree, anf this
won't copy any
>tags files up ... even though they are all in my local
tree from
>my "git fetch linus" pulls from Linus).

Could you push the refs/tags from your tree as well?  Many
of the git
trees on kernel.org have copies of Linus's tags, which
makes it a bit
easier to cross reference.

-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html