From: Sam Ravnborg <sam@ravnborg.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Jesper Nilsson <jesper.nilsson@axis.com>,
mikael.starvik@axis.com, dev-etrax@axis.com,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch v2] cris: proper defconfig setup
Date: Tue, 26 Feb 2008 20:58:02 +0100 [thread overview]
Message-ID: <20080226195802.GD31438@uranus.ravnborg.org> (raw)
In-Reply-To: <20080226195257.GA4898@cs181133002.pp.htv.fi>
>
> Please name the tools that are that broken that they wouldn't apply this
> patch correctly and don't claim my patch was broken (or shut up).
It is only one or two weeks ago we ended up with a zero size file
in the kernel tree - and I do not know why.
I just wanted to make sure we did not see this happen again.
Sam
next prev parent reply other threads:[~2008-02-26 19:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 17:28 [2.6 patch] cris: proper defconfig setup Adrian Bunk
2008-02-26 17:47 ` [2.6 patch v2] " Adrian Bunk
2008-02-26 18:04 ` Jesper Nilsson
2008-02-26 19:44 ` Sam Ravnborg
2008-02-26 19:52 ` Adrian Bunk
2008-02-26 19:58 ` Sam Ravnborg [this message]
2008-02-26 20:05 ` Adrian Bunk
2008-02-26 20:16 ` Sam Ravnborg
2008-02-26 17:53 ` [2.6 patch] " Jesper Nilsson
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=20080226195802.GD31438@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=bunk@kernel.org \
--cc=dev-etrax@axis.com \
--cc=jesper.nilsson@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikael.starvik@axis.com \
/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