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: Thu, 22 Jun 2006 23:28:49 +0000	[thread overview]
Message-ID: <1539.1151018929@ocs3.ocs.com.au> (raw)
In-Reply-To: <200601270107.k0R17838011430@agluck-lia64.sc.intel.com>

"Luck, Tony" (on Thu, 22 Jun 2006 10:34:06 -0700) wrote:
>> BTW, is there any reason that the aegl git tree has no tags?
>
>I haven't thought of any useful way to use tags.  But perhaps it's
>becuase I mostly think of my GIT trees as conduits to Linus/Andrew.
>If you have suggestions on how I can make my trees more useful to
>you by tagging things, then let me know.

Not adding your own tags, but Linus's tags are missing from the ia64
tree.  For some reason, just copying .git/refs/tags from the torvalds
git tree does not work, git-branch complains about invalid objects.  I
thought that tags were portable between trees with common ancestors.

  git-clone .../git/torvalds/linux-2.6.git linux-2.6
  git-clone .../git/aegl/linux-2.6.git linux-2.6-ia64
  cp -a linux-2.6/.git/refs/tags/* linux-2.6-ia64/.git/refs/tags/
  cd linux-2.6-ia64
  git-branch
  error: refs/tags/v2.6.11 does not point to a valid commit object!
  error: refs/tags/v2.6.11-tree does not point to a valid commit object!
  ...
  error: refs/tags/v2.6.17-rc5 does not point to a valid commit object!
  error: refs/tags/v2.6.17-rc6 does not point to a valid commit object!
    origin
    * release
    test



  parent reply	other threads:[~2006-06-22 23:28 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 [this message]
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
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=1539.1151018929@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