All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: sane-srcrevs.inc: moving all svn SRCREVs to recipes
Date: Thu, 01 Apr 2010 19:42:19 +0200	[thread overview]
Message-ID: <hp2ltr$vjd$1@dough.gmane.org> (raw)
In-Reply-To: <1270134711-32158-1-git-send-email-Martin.Jansa@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01-04-10 17:11, Martin Jansa wrote:
> Hi,
> 
> as already said here, global files are common place for conflicts and SRCREV
> belongs to recipe metadata.
> 
> This 2 patches are moving all SRCREVs for svn recipes, with some cleanup in few
> places, like renamed package to show it's from svn, or unified PV to contain
> +svnr${SRCPV}.
> 
> Please ACK or NACK soon as this gets conflicts soon. If there is no NACK in 20 
> hours I would like to push it. Thanks

Looks good to me, we can fix any fallout after applying it. Thanks for
working on this!

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLtNr7MkyGM64RGpERAv+4AJ9+pMv3Ec+gIWgIq7z9CtiruIxJbwCeLrmF
BY9U9XSjqAc+Bo/DDesvBTg=
=VE63
-----END PGP SIGNATURE-----




      parent reply	other threads:[~2010-04-01 17:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 15:11 sane-srcrevs.inc: moving all svn SRCREVs to recipes Martin Jansa
2010-04-01 15:11 ` [PATCH 1/2] EFL: move SRCREVs from sane-srcrevs.inc to efl/e17 recipes Martin Jansa
2010-04-01 15:11 ` [PATCH 2/2] sane-srcrevs: move SRCREVs to recipes Martin Jansa
2010-04-01 15:43   ` Khem Raj
2010-04-01 16:09     ` Martin Jansa
2010-04-01 15:22 ` sane-srcrevs.inc: moving all svn " Richard Purdie
2010-04-01 17:42 ` Koen Kooi [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='hp2ltr$vjd$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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.