All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Trevor Woerner <twoerner@gmail.com>
Cc: "bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>
Subject: Re: [meta-ti] trouble during parsing
Date: Mon, 25 Feb 2013 06:01:08 -0800	[thread overview]
Message-ID: <1361800868.25338.79.camel@ted> (raw)
In-Reply-To: <CAHUNapR3-Z57mPUScW6TnptFbawE3y=+bCcpnTVVfAy-2KjwjA@mail.gmail.com>

On Mon, 2013-02-25 at 08:44 -0500, Trevor Woerner wrote:
> If the purpose of the ls-remote is to match a tag with a hash,
> wouldn't it be easier to just:
> 
>     cat .git/refs/tags/<tagid>
> 
> ?

If the git clone hasn't happened yet, this doesn't work.

> And if the purpose of knowing the tagid is to use that version of the
> code, wouldn't it be easier to just:
> 
>     git checkout <tagid>

That isn't the only purpose.

Cheers,

Richard




  reply	other threads:[~2013-02-25 14:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20 12:54 trouble during parsing Andreas Müller
2013-02-20 14:31 ` Chris Larson
2013-02-25  2:12   ` Flanagan, Elizabeth
2013-02-25  2:28     ` Flanagan, Elizabeth
2013-02-25  9:32       ` Andreas Müller
2013-02-25  9:32         ` [bitbake-devel] " Andreas Müller
2013-02-25  9:46         ` [meta-ti] " Javier Martinez Canillas
2013-02-25  9:46           ` [bitbake-devel] " Javier Martinez Canillas
2013-02-25 10:02           ` [meta-ti] " Andreas Müller
2013-02-25 10:02             ` [bitbake-devel] " Andreas Müller
2013-02-25 13:44             ` [meta-ti] " Trevor Woerner
2013-02-25 14:01               ` Richard Purdie [this message]
2013-02-25 14:07                 ` Gary Thomas
2013-02-25 15:24                   ` Trevor Woerner
2013-02-25 14:32             ` Denys Dmytriyenko
2013-02-25 14:32               ` [bitbake-devel] " Denys Dmytriyenko
2013-02-25 15:13       ` Jason Wessel

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=1361800868.25338.79.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=twoerner@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.