From: Jeremy Rosen <jeremy.rosen@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] prevent recursion in %_defconfig rules
Date: Mon, 20 Jan 2014 09:03:14 +0100 (CET) [thread overview]
Message-ID: <1645253426.4507611.1390204994729.JavaMail.root@openwide.fr> (raw)
In-Reply-To: <20140117195405.GC3982@free.fr>
> >
> > J?r?my, can you describe your setup, so we can try to reproduce it,
> > and
> > find a proper fix?
>
Ok, i'll look into it and try to figure out...
it's really weird that you were not able to reproduce with the steps
in the patch, it was pretty systematic for me. I'll try to reproduce
and report whatever I find
next prev parent reply other threads:[~2014-01-20 8:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 16:22 [Buildroot] [PATCH] prevent recursion in %_defconfig rules Jérémy Rosen
2014-01-13 8:52 ` Jeremy Rosen
2014-01-13 8:59 ` Peter Korsgaard
2014-01-17 17:52 ` Yann E. MORIN
2014-01-17 18:09 ` Yann E. MORIN
2014-01-17 19:54 ` Yann E. MORIN
2014-01-20 8:03 ` Jeremy Rosen [this message]
2014-01-20 8:13 ` Jeremy Rosen
2014-01-20 18:31 ` Yann E. MORIN
2014-01-20 22:58 ` Romain Naour
2014-01-20 23:58 ` Yann E. MORIN
2014-01-21 8:44 ` Jeremy Rosen
2014-01-21 18:38 ` Yann E. MORIN
2014-01-22 14:16 ` Jeremy Rosen
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=1645253426.4507611.1390204994729.JavaMail.root@openwide.fr \
--to=jeremy.rosen@openwide.fr \
--cc=buildroot@busybox.net \
/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