From: Roland Hieber <r.hieber@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 1/4] doc: document git patch workflow
Date: Fri, 14 Jul 2017 14:28:40 +0200 [thread overview]
Message-ID: <da29f79a-eda4-fdef-bf4a-9fd5bc04cb1d@pengutronix.de> (raw)
In-Reply-To: <6ebe3654-12c9-9a52-1807-282c6b2cf092@pengutronix.de>
On 14.07.2017 14:21, Bastian Stender wrote:
>> +.. note:: Optionally, you can enable the setting *Developer Options →
>> use git to
>> + apply patches* in `ptxdist setup` to enable this permanently.
>> + However, note that this setting is still experimental.
>
> Maybe we should mention that this can lead to unexpected side effects. I
> remember debugging a package configured with autoconf and AX_IS_RELEASE:
>
> https://www.gnu.org/software/autoconf-archive/ax_is_release.html
>
> This lead to treating warnings as errors with "use git to apply patches"
> and thus compilation failed.
Yes, I remembered something like that, but I couldn't reproduce the
exact error so I just formulated it generally.
>> +After commit your patches, call ``git ptx-patches`` to regenerate the
>> patches
>> +and the series file in the ``patches/foo-0.1`` folder, so they don't
>> get lost
>> +when cleaning the package.
>
> This should be consistent, so ``patches/foo-1.1.0``.
Oh, I changed it afterwards and overlooked that one. Thanks, will send v2.
- Roland
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-07-14 12:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 10:57 Roland Hieber
2017-07-14 10:57 ` [ptxdist] [PATCH 2/4] doc: promote faq to own section Roland Hieber
2017-07-14 10:57 ` [ptxdist] [PATCH 3/4] doc: faq: apply more structure Roland Hieber
2017-07-14 12:35 ` Michael Olbrich
2017-07-14 10:57 ` [ptxdist] [PATCH 4/4] doc: faq: copy editing, small rewrites for more clarity Roland Hieber
2017-07-14 12:34 ` Michael Olbrich
2017-07-14 12:21 ` [ptxdist] [PATCH 1/4] doc: document git patch workflow Bastian Stender
2017-07-14 12:28 ` Roland Hieber [this message]
2017-07-14 12:42 ` Michael Olbrich
2017-07-17 6:49 ` Uwe Kleine-König
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=da29f79a-eda4-fdef-bf4a-9fd5bc04cb1d@pengutronix.de \
--to=r.hieber@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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