From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Cc: Michael 'Mickey' Lauer <mickey@openmoko.org>
Subject: Re: The ongoing SRCREV saga
Date: Thu, 13 Sep 2007 09:45:47 +0100 [thread overview]
Message-ID: <1189673147.6326.5.camel@localhost.localdomain> (raw)
In-Reply-To: <46E8ED0F.5000003@student.utwente.nl>
On Thu, 2007-09-13 at 09:55 +0200, Koen Kooi wrote:
> Richard Purdie schreef:
> > Are there any objections to the above? I'll probably commit this fairly
> > quickly if the openmoko devs are agreeable.
>
> Mickey OK'ed it on another list, so I added sane-srcrevs.inc to angstrom. (in)sane-srcrevs
> and moko-autorev needs some tweaking, but 90% is there.
Thanks for that, I've completed the change tweaking these files a little
and changing the default SRCREV definition as discussed.
Cheers,
Richard
next prev parent reply other threads:[~2007-09-13 8:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 23:01 The ongoing SRCREV saga Richard Purdie
2007-09-13 1:30 ` mwester
2007-09-13 7:55 ` Koen Kooi
2007-09-13 8:45 ` Richard Purdie [this message]
[not found] <1189635624.6480.129.camel@localhost.localdomain>
2007-09-12 23:47 ` Michael 'Mickey' Lauer
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=1189673147.6326.5.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=mickey@openmoko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox