From: Otavio Salvador <otavio@debian.org>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: OE weekly changelog 2009-01-12 to 2009-01-19
Date: Wed, 21 Jan 2009 11:58:06 -0200 [thread overview]
Message-ID: <87hc3s2235.fsf@neumann.lab.ossystems.com.br> (raw)
In-Reply-To: <f96d234e0901210529q57d4abf1s98295b7160d6d2da@mail.gmail.com> (Cliff Brake's message of "Wed\, 21 Jan 2009 08\:29\:05 -0500")
Cliff Brake <cliff.brake@gmail.com> writes:
> On Tue, Jan 20, 2009 at 2:00 PM, Tom Rini <trini@kernel.crashing.org> wrote:
>> On Tue, Jan 20, 2009 at 11:40:03AM -0500, Cliff Brake wrote:
>>
>>> OE weekly changelog 2009-01-12 to 2009-01-19
>>
>> Hmm, this missed pulling in rpurdie/canadian-sofar into the main branch.
>
> Thanks for pointing that out -- I'll see if I can update the script to
> included merges like that.
Personally I think that it is better to keep --no-merges otherwise it
will be poluted and it won't give you the idea of what was pulled
anyway.
If someone wants to know where something has been introduced, it is
much better to use gitk or similar.
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
prev parent reply other threads:[~2009-01-21 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 16:40 OE weekly changelog 2009-01-12 to 2009-01-19 Cliff Brake
2009-01-20 19:00 ` Tom Rini
2009-01-21 13:29 ` Cliff Brake
2009-01-21 13:58 ` Otavio Salvador [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=87hc3s2235.fsf@neumann.lab.ossystems.com.br \
--to=otavio@debian.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.