From: "Petr Štetiar" <ynezz@true.cz>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] socat: Add version 1.7.1.2
Date: Sat, 23 Jan 2010 21:57:32 +0100 [thread overview]
Message-ID: <20100123205732.GQ18793@ibawizard.net> (raw)
In-Reply-To: <1264276434.3738.53.camel@mattotaupa.wohnung.familie-menzel.net>
Paul Menzel <paulepanter@users.sourceforge.net> [2010-01-23 20:53:54]:
> 1. Applying your patch gives me warnings.
>
> $ git am /tmp/\[oe\]_\[PATCH\]_socat\:_Add_version_1.7.1.2
> Applying: socat: Add version 1.7.1.2
> /srv/filme/oe/openembedded/.git/rebase-apply/patch:29: trailing whitespace.
>
> /srv/filme/oe/openembedded/.git/rebase-apply/patch:38: trailing whitespace.
>
> /srv/filme/oe/openembedded/.git/rebase-apply/patch:46: trailing whitespace.
>
> /srv/filme/oe/openembedded/.git/rebase-apply/patch:54: trailing whitespace.
>
> /srv/filme/oe/openembedded/.git/rebase-apply/patch:60: space before tab in indent.
> IF_IP6 ("ipv6only", &opt_ipv6_v6only)
> warning: squelched 13 whitespace errors
> warning: 18 lines add whitespace errors.
Those are warnings "only", just whitespace errors. It was applied anyway,
right? I think, it's because git don't like upstream code much.
-- ynezz
next prev parent reply other threads:[~2010-01-23 20:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 19:03 [PATCH] socat: Add version 1.7.1.2 John Faith
2010-01-23 19:37 ` Koen Kooi
2010-01-23 19:59 ` John Faith
2010-01-23 21:51 ` What set the state in Patchwork to? (was: [PATCH] socat: Add version 1.7.1.2) Paul Menzel
2010-01-23 19:53 ` [PATCH] socat: Add version 1.7.1.2 Paul Menzel
2010-01-23 20:57 ` Petr Štetiar [this message]
2010-01-23 22:31 ` John Faith
2010-01-23 22:54 ` Paul Menzel
2010-01-23 23:47 ` Petr Štetiar
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=20100123205732.GQ18793@ibawizard.net \
--to=ynezz@true.cz \
--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.