From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] gnuconfig not up to date, but update gives conflicts during merge
Date: Mon, 9 Jul 2007 20:22:22 +0200 [thread overview]
Message-ID: <20070709182222.GA24951@aon.at> (raw)
In-Reply-To: <1183954608.5534.32.camel@elrond.sweden.atmel.com>
On Mon, Jul 09, 2007 at 06:16:48AM +0200, Ulf Samuelsson wrote:
>Checked if gnuconfig was up to date
>Seems it was not, but cvs up was not clean.
>What do we do?
We usually update if needed. This message leads me to think that you
require (or at least want) it to be updated. Well, try r19055
prev parent reply other threads:[~2007-07-09 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 4:16 [Buildroot] gnuconfig not up to date, but update gives conflicts during merge Ulf Samuelsson
2007-07-09 18:22 ` Bernhard Fischer [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=20070709182222.GA24951@aon.at \
--to=rep.dot.nop@gmail.com \
--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