mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Roland Hieber <rhi@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] doc: dev_patching: remove outdated note about 'extract --git'
Date: Thu, 16 Mar 2023 15:31:24 +0100	[thread overview]
Message-ID: <20230316143124.3677753-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230309131342.3717841-1-rhi@pengutronix.de>

Thanks, applied as d82210987aab0614d5a83c0cb924fe3fcd391b21.

Michael

[sent from post-receive hook]

On Thu, 16 Mar 2023 15:31:24 +0100, Roland Hieber <rhi@pengutronix.de> wrote:
> Such problems should no longer occur since commit 48f2895f519004d9fa4a
> (2023-03-03, Michael Olbrich: "ptxd_make_world_init: make sure git from
> 'ptxdist --git extract ...' is ignored").
> 
> Signed-off-by: Roland Hieber <rhi@pengutronix.de>
> Message-Id: <20230309131342.3717841-1-rhi@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/doc/dev_patching.rst b/doc/dev_patching.rst
> index a17983aa826a..d2a261636a02 100644
> --- a/doc/dev_patching.rst
> +++ b/doc/dev_patching.rst
> @@ -127,9 +127,6 @@ and import the package source as the first commit.
>  .. note:: Optionally, you can enable the setting *Developer Options →
>    use git to apply patches* in `ptxdist setup` to get this behaviour
>    as a default for every package.
> -  However, note that this setting is meant for development only, and can lead
> -  to failures – some packages try to determine if they are being compiled from
> -  a Git source tree, and behave differently in that case.
>  
>  Then you can change into the package build directory
>  (``platform-<name>/build-target/foo-1.1.0``),



      reply	other threads:[~2023-03-16 14:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09 13:13 [ptxdist] [PATCH] " Roland Hieber
2023-03-16 14:31 ` Michael Olbrich [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=20230316143124.3677753-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=rhi@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