From: JongSeok Won <wjs890204@gmail.com>
To: ofono@ofono.org
Subject: Re: [PATCH] build: require glib >= 2.60
Date: Mon, 08 Mar 2021 18:22:47 +0900 [thread overview]
Message-ID: <CAKnLNuTVeg5pN-6w9-GQV=NLYOSf9ajG0V7b8oBbmLogXNH9Hw@mail.gmail.com> (raw)
In-Reply-To: <718f5a16-8605-c043-e95b-299eeab44476@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
Hi, Denis
I had a mistake while making patch. So, I'll re-send the patch of V2.
Best regards
JongSeok Won
2021년 3월 5일 (금) 오후 11:49, Denis Kenzior <denkenz@gmail.com>님이 작성:
> Hi,
>
> > -PKG_CHECK_MODULES(GLIB, glib-2.0 >= 2.32, dummy=yes,
> > - AC_MSG_ERROR(GLib >= 2.32 is required))
> > +PKG_CHECK_MODULES(GLIB, glib-2.0 >= 2.60, dummy=yes,
> > + AC_MSG_ERROR(GLib >= 2.60 is required))
>
> This patch doesn't apply:
> denkenz(a)localhost ~/ofono-master $ git am ~/merge/\[PATCH\]\ build\:\
> require\
> glib\ \>\=\ 2.60.eml
> Applying: build: require glib >= 2.60
> error: corrupt patch at line 12
> Patch failed at 0001 build: require glib >= 2.60
> hint: Use 'git am --show-current-patch=diff' to see the failed patch
> When you have resolved this problem, run "git am --continue".
> If you prefer to skip this patch, run "git am --skip" instead.
> To restore the original branch and stop patching, run "git am --abort".
>
> Looks like it is whitespace-mangled or otherwise damaged for some reason.
>
> Regards,
> -Denis
>
[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 1510 bytes --]
next prev parent reply other threads:[~2021-03-08 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 5:41 [PATCH] build: require glib >= 2.60 JongSeok Won
2021-03-05 14:49 ` Denis Kenzior
2021-03-08 9:22 ` JongSeok Won [this message]
2021-03-08 9:33 ` JongSeok Won
2021-04-30 14:47 ` Denis Kenzior
-- strict thread matches above, loose matches on Subject: below --
2021-02-16 9:31 JongSeok Won
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='CAKnLNuTVeg5pN-6w9-GQV=NLYOSf9ajG0V7b8oBbmLogXNH9Hw@mail.gmail.com' \
--to=wjs890204@gmail.com \
--cc=ofono@ofono.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.