linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@freescale.com>
To: John Linn <John.Linn@xilinx.com>
Cc: alan.casey5@mail.dcu.ie, wangyanlong <killyouatonce@gmail.com>,
	linuxppc-embedded@ozlabs.org
Subject: Re: Linux issues on Xilinx XUPV2P board
Date: Fri, 15 Aug 2008 10:08:19 -0500	[thread overview]
Message-ID: <48A59BE3.7000709@freescale.com> (raw)
In-Reply-To: <20080815145328.670D4C7004F@mail23-sin.bigfish.com>

John Linn wrote:
> Ah I see, sorry about that, misunderstood what was needed.
> 
> So there may be other ways as I'm not a Git expert, but I clone the
> repository, then reset to the a Git tag.
> 
>> git reset --hard <tag name>
> 
> We're working on a new frame buffer driver for a new core, but the old
> frame buffer has not been high priority for us.
> 
> Thanks,
> John 

While this "Works" in the sense that it makes your working
directory look like the contents of the given tag, you are
now using a "detached HEAD" -- ie, no real branch.

If you think you will ever want to make a change or check
in something, you might be better to create a branch based
on the original tag, perhaps something like:

    $ git checkout -b my-v2.6.24 v2.6.24

HTH,
jdl

  reply	other threads:[~2008-08-15 15:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 15:18 Linux issues on Xilinx XUPV2P board Alan Casey
2008-08-15  8:43 ` wangyanlong
2008-08-15  9:59   ` Alan Casey
2008-08-15 11:35     ` wangyanlong
2008-08-15 12:34       ` Alan Casey
2008-08-15 14:30         ` John Linn
2008-08-15 14:36           ` Alan Casey
2008-08-15 14:53             ` John Linn
2008-08-15 15:08               ` Jon Loeliger [this message]
2008-08-15 14:31         ` wangyanlong
2008-08-15 14:50           ` Alan Casey
2008-08-31 15:58             ` wangyanlong

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=48A59BE3.7000709@freescale.com \
    --to=jdl@freescale.com \
    --cc=John.Linn@xilinx.com \
    --cc=alan.casey5@mail.dcu.ie \
    --cc=killyouatonce@gmail.com \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).