All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: "angstrom-distro-devel@linuxtogo.org"
	<angstrom-distro-devel@linuxtogo.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [oe] OE Changelog for 2011-10-17 to 2011-10-24
Date: Thu, 27 Oct 2011 22:35:52 -0400	[thread overview]
Message-ID: <20111028023552.GR15391@denix.org> (raw)
In-Reply-To: <CAOd_LFw0kBsf-NDpUQ-rUHxYP+v_5Ff3nuSNTUK3QuSrB5_eHw@mail.gmail.com>

On Thu, Oct 27, 2011 at 10:06:32PM -0400, Cliff Brake wrote:
> On Thursday, October 27, 2011, Denys Dmytriyenko <denis@denix.org> wrote:
> > On Thu, Oct 27, 2011 at 04:40:53PM -0400, cliff.brake@gmail.com wrote:
> >> Changelog for 2011-10-17 to 2011-10-24.  Projects included in this
> report:
> >
> > FYI, I think you have a bug in your scripts, where it misses commits made
> on
> > Monday, that were not included in the previous ChangeLog and they are
> being
> > skipped in this one...
> 
> Can you give me an example of a commit that got missed and I'll debug?

Well, it's not like I specifically verify that all my patches get mentioned in 
the ChangeLog... :) But just glancing over it struck me that only u-boot 
related ones were listed:

Changelog for meta-texasinstruments:
Denys Dmytriyenko (3):
  u-boot-2011.10rc: update to cover ti33x SOC boards, not just beaglebone
  u-boot 2011.10rc: update with latest rev and new SRC_URI
  u-boot 2011.10rc: update to the latest revision

So, I checked the previous ChangeLog and couldn't find others from the same 
series, such as:
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/commit/?id=2c8dcc2a8c16792c8a765a70109cc2462b83018e
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/commit/?id=3b5eced12a10a3809f60df256b8f952c2286af4d
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/commit/?id=98cca8ea1d324a1a59b7d96838952a579c72b419

While, of course, the commits in question are still there, your ChangeLogs 
provide additional informational benefits to the Community. So, I figured, you 
might want to fix that small issue in the script to make it even better... :)


> > Also, can you please include meta-ti@yoctoproject.org as the official
> mailing
> > list for meta-ti/meta-texasinstruments BSP layer. Thanks.
> 
> Ill look into something like that.  We currently don't have any type of
> email field, but something could be added.

No, I meant to add it to the distribution list, i.e. send future ChangeLogs 
also to meta-ti@yoctoproject.org mailing list, along with oe-core, oe-dev and 
angstrom lists. Unless you think it's overkill. Thanks.

-- 
Denys



WARNING: multiple messages have this Message-ID (diff)
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: "angstrom-distro-devel@linuxtogo.org"
	<angstrom-distro-devel@linuxtogo.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] OE Changelog for 2011-10-17 to 2011-10-24
Date: Thu, 27 Oct 2011 22:35:52 -0400	[thread overview]
Message-ID: <20111028023552.GR15391@denix.org> (raw)
In-Reply-To: <CAOd_LFw0kBsf-NDpUQ-rUHxYP+v_5Ff3nuSNTUK3QuSrB5_eHw@mail.gmail.com>

On Thu, Oct 27, 2011 at 10:06:32PM -0400, Cliff Brake wrote:
> On Thursday, October 27, 2011, Denys Dmytriyenko <denis@denix.org> wrote:
> > On Thu, Oct 27, 2011 at 04:40:53PM -0400, cliff.brake@gmail.com wrote:
> >> Changelog for 2011-10-17 to 2011-10-24.  Projects included in this
> report:
> >
> > FYI, I think you have a bug in your scripts, where it misses commits made
> on
> > Monday, that were not included in the previous ChangeLog and they are
> being
> > skipped in this one...
> 
> Can you give me an example of a commit that got missed and I'll debug?

Well, it's not like I specifically verify that all my patches get mentioned in 
the ChangeLog... :) But just glancing over it struck me that only u-boot 
related ones were listed:

Changelog for meta-texasinstruments:
Denys Dmytriyenko (3):
  u-boot-2011.10rc: update to cover ti33x SOC boards, not just beaglebone
  u-boot 2011.10rc: update with latest rev and new SRC_URI
  u-boot 2011.10rc: update to the latest revision

So, I checked the previous ChangeLog and couldn't find others from the same 
series, such as:
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/commit/?id=2c8dcc2a8c16792c8a765a70109cc2462b83018e
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/commit/?id=3b5eced12a10a3809f60df256b8f952c2286af4d
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/commit/?id=98cca8ea1d324a1a59b7d96838952a579c72b419

While, of course, the commits in question are still there, your ChangeLogs 
provide additional informational benefits to the Community. So, I figured, you 
might want to fix that small issue in the script to make it even better... :)


> > Also, can you please include meta-ti@yoctoproject.org as the official
> mailing
> > list for meta-ti/meta-texasinstruments BSP layer. Thanks.
> 
> Ill look into something like that.  We currently don't have any type of
> email field, but something could be added.

No, I meant to add it to the distribution list, i.e. send future ChangeLogs 
also to meta-ti@yoctoproject.org mailing list, along with oe-core, oe-dev and 
angstrom lists. Unless you think it's overkill. Thanks.

-- 
Denys



  reply	other threads:[~2011-10-28  3:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-27 20:40 OE Changelog for 2011-10-17 to 2011-10-24 cliff.brake
2011-10-27 21:09 ` [oe] " Denys Dmytriyenko
2011-10-27 21:09   ` Denys Dmytriyenko
2011-10-28  2:06   ` Cliff Brake
2011-10-28  2:06     ` [OE-core] " Cliff Brake
2011-10-28  2:35     ` Denys Dmytriyenko [this message]
2011-10-28  2:35       ` 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=20111028023552.GR15391@denix.org \
    --to=denis@denix.org \
    --cc=angstrom-distro-devel@linuxtogo.org \
    --cc=openembedded-core@lists.openembedded.org \
    --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.