public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: patches added to release/test trees
Date: Sat, 24 Jun 2006 08:10:12 +0000	[thread overview]
Message-ID: <23024.1151136612@ocs3.ocs.com.au> (raw)
In-Reply-To: <200601270107.k0R17838011430@agluck-lia64.sc.intel.com>

"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.


  parent reply	other threads:[~2006-06-24  8:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-27  1:07 patches added to release/test trees Luck, Tony
2006-02-03  0:03 ` Luck, Tony
2006-02-08 23:14 ` Luck, Tony
2006-04-06 23:49 ` Luck, Tony
2006-06-21 23:19 ` Luck, Tony
2006-06-22  0:33 ` Keith Owens
2006-06-22  2:44 ` Keith Owens
2006-06-22  3:28 ` Horms
2006-06-22 17:34 ` Luck, Tony
2006-06-22 23:28 ` Keith Owens
2006-06-23  0:11 ` Andreas Schwab
2006-06-23  0:29 ` Keith Owens
2006-06-23 17:08 ` Luck, Tony
2006-06-24  8:10 ` Keith Owens [this message]
2006-06-25 22:51 ` Luck, Tony
2006-06-26  8:59 ` Horms
2006-06-26 17:23 ` Luck, Tony
2006-06-27  8:03 ` Keith Owens

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=23024.1151136612@ocs3.ocs.com.au \
    --to=kaos@sgi.com \
    --cc=linux-ia64@vger.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