Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Michael Smith <msmith@cbnco.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: TSC Meetings for the meeting of June
Date: Wed, 09 Jun 2010 09:25:12 -0400	[thread overview]
Message-ID: <4C0F9638.8040802@cbnco.com> (raw)
In-Reply-To: <4C0F9119.3000909@freyther.de>

Holger Freyther wrote:
>   c.) To ease this for existing users and to reduce the amount of
>       support org.openembedded.dev will track master and remains
>       available for a limited but long amount of time.

> The TSC is not sure on how to implement c.) and this will determine when
> we will be able to switch over and the schedule of doing so.

This should work (on the bare repo):

git branch -m org.openembedded.dev master
git symbolic-ref refs/heads/org.openembedded.dev refs/heads/master

(thanks 
http://stackoverflow.com/questions/549920/is-it-possible-to-alias-a-branch-in-git)

Mike



  reply	other threads:[~2010-06-09 13:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 13:03 TSC Meetings for the meeting of June Holger Freyther
2010-06-09 13:25 ` Michael Smith [this message]
2010-06-09 13:53 ` Frans Meulenbroeks
2010-06-09 14:57   ` Chris Larson
2010-06-09 16:53     ` Philip Balister
2010-06-09 17:37       ` Khem Raj
2010-06-11  8:06         ` Frans Meulenbroeks
2010-06-11 18:29   ` Koen Kooi
2010-06-11 21:37     ` Richard Purdie
2010-06-12  7:37       ` Koen Kooi
2010-06-12 11:12       ` Frans Meulenbroeks
2010-06-12 11:47         ` Graeme Gregory
2010-06-12 12:20           ` Frans Meulenbroeks
2010-06-30 10:26 ` Holger Freyther
2010-06-30 11:05   ` Koen Kooi
2010-06-30 13:04     ` Frans Meulenbroeks
2010-06-30 13:19     ` Holger Freyther
2010-07-01  8:56       ` Koen Kooi
2010-07-01 11:52         ` Frans Meulenbroeks
2010-07-01 12:07           ` Graeme Gregory
2010-07-01 13:43             ` Frans Meulenbroeks
2010-07-01 17:59               ` Mark Brown

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=4C0F9638.8040802@cbnco.com \
    --to=msmith@cbnco.com \
    --cc=openembedded-devel@lists.openembedded.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