All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: testing 2010-10-04
Date: Tue, 5 Oct 2010 16:00:14 +0200	[thread overview]
Message-ID: <20101005140014.GF3517@excalibur.local> (raw)
In-Reply-To: <AANLkTikaunRh8wSWihAN3C9xh++YBH2qZT8Tr_xdxVF-@mail.gmail.com>

Hello.

On Tue, 2010-10-05 at 15:23, Frans Meulenbroeks wrote:
> 
> Personally I would prefer it if the testing branch could be made on friday.
> That way I (and I guess others) can use unused CPU cycles @ work
> during the weekend to do the test builds.
> How do others feel about that?

I think it makes sense. I normally do the build directly after the new testing
branch gets created and doing that at a weekend would be good from my view. Put
monday is not that bad either.

Cliff, for now you have done all the branch creating and tagging, etc. Thanks
for that. If you need help or some weeks relaxing from the monotone tasks let us
know.

regards
Stefan Schmidt



  reply	other threads:[~2010-10-05 14:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04 18:05 testing 2010-10-04 Cliff Brake
2010-10-05 10:27 ` Frans Meulenbroeks
2010-10-05 11:39   ` Frans Meulenbroeks
2010-10-05 14:21     ` Cliff Brake
2010-10-05 12:32 ` Stefan Schmidt
2010-10-05 13:23   ` Frans Meulenbroeks
2010-10-05 14:00     ` Stefan Schmidt [this message]
2010-10-05 14:24     ` Cliff Brake
2010-10-05 13:28   ` Koen Kooi
2010-10-05 13:57     ` Stefan Schmidt
2010-10-05 14:50   ` dfoley
2010-10-06 10:37     ` Stefan Schmidt
2010-10-07 15:34       ` dfoley
2010-10-07 18:26         ` Khem Raj
2010-10-07 19:04           ` Dallas Foley
2010-10-08  5:44             ` Stefan Schmidt

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=20101005140014.GF3517@excalibur.local \
    --to=stefan@datenfreihafen.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.