From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andreas Oberritter <obi@opendreambox.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] dpkg-native: Avoid 'file changed' errors from tar
Date: Mon, 30 Mar 2015 21:24:57 +0100 [thread overview]
Message-ID: <1427747097.14020.323.camel@linuxfoundation.org> (raw)
In-Reply-To: <551990D2.10904@opendreambox.org>
On Mon, 2015-03-30 at 20:07 +0200, Andreas Oberritter wrote:
> On 30.03.2015 18:21, Otavio Salvador wrote:
> > On Mon, Mar 30, 2015 at 1:02 PM, Richard Purdie
> > <richard.purdie@linuxfoundation.org> wrote:
> >> On Mon, 2015-03-30 at 12:02 -0300, Otavio Salvador wrote:
> >>> +When running do_package_write_deb, we have trees of symlinked files
>
> Richard, did you intend to write "hardlinked" here?
I did, yes. I'll correct that, thanks.
> It's my impression that if Richard had omitted the first sentence of his
> commit message, the message would still have been descriptive enough,
> and nobody would ever have complained.
That is the impression I got too. Its odd that a comment intended to
help the user find more information should generate this discussion,
particularly as the details in the patch header are more implementation
oriented and make sense when you're looking at the dpkg code (which you
can in the patch).
So I may simply remove the comment that is causing contention.
Cheers,
Richard
prev parent reply other threads:[~2015-03-30 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 8:50 [PATCH] dpkg-native: Avoid 'file changed' errors from tar Richard Purdie
2015-03-30 13:52 ` Otavio Salvador
2015-03-30 14:58 ` Richard Purdie
2015-03-30 15:02 ` Otavio Salvador
2015-03-30 16:02 ` Richard Purdie
2015-03-30 16:21 ` Otavio Salvador
2015-03-30 16:37 ` Mark Hatle
2015-03-30 17:13 ` Mark Hatle
2015-03-30 18:07 ` Andreas Oberritter
2015-03-30 20:24 ` Richard Purdie [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=1427747097.14020.323.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=obi@opendreambox.org \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox