Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: meta-browser duplicate patch
Date: Thu, 12 Jan 2017 09:44:14 -0500	[thread overview]
Message-ID: <20170112144413.GA7854@linux-uys3> (raw)

Does the do_patch logic now ignore the same patch being applied twice? I was
quite sure this was a problem in the past (and if it isn't, maybe it should
be?)

In commit fb4e542079958b6afde324a1e9bfdd695842aeeb
the patch recipes-browser/chromium/chromium/chromium/Do-not-depend-on-Linux-4.5.patch

and in commit c6fc9da7be64af7cd08c2bbb026e4c3ffc760687
the patch recipes-browser/chromium/chromium/chromium/unset-madv-free.patch

are exactly the same. Yet they're both happily applied without so much as a
warning, not even in temp/log.do_patch.


             reply	other threads:[~2017-01-12 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 14:44 Trevor Woerner [this message]
2017-01-12 14:59 ` meta-browser duplicate patch Alexander Kanavin
2017-01-12 15:20   ` Trevor Woerner

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=20170112144413.GA7854@linux-uys3 \
    --to=twoerner@gmail.com \
    --cc=openembedded-devel@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