All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe MacDonald <Joe_MacDonald@mentor.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: Recipe Name Change
Date: Tue, 10 Mar 2015 17:28:33 -0400	[thread overview]
Message-ID: <20150310212832.GA4083@mentor.com> (raw)
In-Reply-To: <CAL0pqZ15mf+jANcqzD=EAYs-BOKThCdWdzO2J2aRaV1v4moO=g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 888 bytes --]

[[oe] Recipe Name Change] On 15.03.10 (Tue 11:59) Leah wrote:

> Hi,
> 
> We have recently changed the name of our product from CyaSSL to wolfSSL. I
> would like to update to a recipe reflecting this name. Our current recipe
> is located at
> https://github.com/openembedded/meta-oe/tree/master/meta-networking/recipes-connectivity/cyassl.
> Should I make a commit to delete cyassl and a separate commit to add the
> new wolfssl recipe? Or should this be done in one commit?

I would rather see it done as a 'git mv', meaning one commit, with the
proper migration path variables added either in the same commit (the
diffs will still be nice and clean when you do a -M on them) as Khem
described.

-J.

> 
> Thanks,
> 
> Leah
> 
> 
> -- 
> 
> Leah Thompson
> www.wolfssl.com
> leah@wolfssl.com
> 406-570-1389
> Skype: lchristina26
-- 
-Joe MacDonald.
:wq

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 501 bytes --]

      parent reply	other threads:[~2015-03-10 21:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 17:59 Recipe Name Change Leah
2015-03-10 18:27 ` Khem Raj
2015-03-10 18:37 ` Martin Jansa
2015-03-10 21:28 ` Joe MacDonald [this message]

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=20150310212832.GA4083@mentor.com \
    --to=joe_macdonald@mentor.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 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.