From: Peter Maydell <peter.maydell@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Dan Streetman <ddstreet@canonical.com>,
Michael Tokarev <mjt@tls.msk.ru>,
QEMU Developers <qemu-devel@nongnu.org>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>,
Rafael David Tinoco <rafael.tinoco@canonical.com>
Subject: Re: [PATCH] configure: actually disable 'git_update' mode with --disable-git-update
Date: Fri, 2 Oct 2020 15:25:12 +0100 [thread overview]
Message-ID: <CAFEAcA-PGNqugn-deNMJv1v49GRB=8UbhXYL3Fpko9do4+rsWQ@mail.gmail.com> (raw)
In-Reply-To: <20201002131130.GB2338114@redhat.com>
On Fri, 2 Oct 2020 at 14:13, Daniel P. Berrangé <berrange@redhat.com> wrote:
> Assuming you're just using git for conveniently applying local
> downstream patches, you don't need the git repo to exist once
> getting to the build stage. IOW just delete the .git dir after
> applying patches before running a build.
...then what do you do if the build fails and you want to
edit/update the patch before retrying? "Blow away your .git
tree every time you build and reconstitute it somehow later"
doesn't seem like a very friendly thing to require...
thanks
-- PMM
next prev parent reply other threads:[~2020-10-02 14:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200715205013.2367760-1-ddstreet@canonical.com>
[not found] ` <20200716102213.2931209-1-ddstreet@canonical.com>
2020-07-24 9:55 ` [PATCH v2] configure: actually disable 'git_update' mode with --disable-git-update Michael Tokarev
2020-07-29 19:58 ` [PATCH] " Dan Streetman
2020-09-13 18:57 ` [PATCH resend] " Dan Streetman
2020-09-13 21:09 ` Philippe Mathieu-Daudé
2020-09-22 16:34 ` [PATCH] " Daniel P. Berrangé
2020-10-01 1:28 ` Dan Streetman
2020-10-02 13:11 ` Daniel P. Berrangé
2020-10-02 14:25 ` Peter Maydell [this message]
2020-10-02 14:44 ` Rafael David Tinoco
2020-10-16 20:51 ` Dan Streetman
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='CAFEAcA-PGNqugn-deNMJv1v49GRB=8UbhXYL3Fpko9do4+rsWQ@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=berrange@redhat.com \
--cc=christian.ehrhardt@canonical.com \
--cc=ddstreet@canonical.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=rafael.tinoco@canonical.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;
as well as URLs for NNTP newsgroup(s).