From: Jacob Stiffler <j-stiffler@ti.com>
To: Denys Dmytriyenko <denys@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH 1/2] ti-sysbios: Add version 6.41.04.54.
Date: Tue, 28 Jul 2015 11:16:28 -0400 [thread overview]
Message-ID: <55B79CCC.70604@ti.com> (raw)
In-Reply-To: <20150709232111.GJ15657@edge>
Denys,
Were these not in the correct order? Add new version first, then remove
the old version, correct?
Do you want me to resubmit these patch sets??
- Jake
On 7/9/2015 7:21 PM, Denys Dmytriyenko wrote:
> Jake,
>
> I think that was one of the long standing confusion - back in OpenEmbedded
> Classic days removing old version wasn't safe, as it could break someone
> else's build. So, people were advised to add new version they wanted, but send
> a separate patch that deleted the old one. If there was someone who used that
> specific old version, they could object to the second patch. That's why there
> used to be multiple versions of the same recipes all over the place. Now, with
> OpenEmbedded Core and the Yocto Project, the normal policy is to keep a single
> version of each recipe, where possible. Hence, updating recipe version is
> better done in a single patch, as it allows tracking recipe changes across
> versions with git log --follow flag. Other than that, I don't remember any
> other reason why would you want to do a version update in 2 separate patches.
> My position was always less strict - if you want 2 patches, then at least send
> them in right order, plus using -C --find-copies-harder flags would help with
> review, as it wouldn't look like 100% new file...
>
next prev parent reply other threads:[~2015-07-28 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 12:29 [PATCH 1/2] ti-sysbios: Add version 6.41.04.54 Jacob Stiffler
2015-07-07 12:29 ` [PATCH 2/2] ti-sysbios: Remove version 6.41.02.41 Jacob Stiffler
2015-07-07 20:59 ` [PATCH 1/2] ti-sysbios: Add version 6.41.04.54 Denys Dmytriyenko
2015-07-08 10:51 ` Jacob Stiffler
2015-07-09 23:21 ` Denys Dmytriyenko
2015-07-28 15:16 ` Jacob Stiffler [this message]
2015-07-28 19:11 ` Denys Dmytriyenko
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=55B79CCC.70604@ti.com \
--to=j-stiffler@ti.com \
--cc=denys@ti.com \
--cc=meta-ti@yoctoproject.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.