From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] buildhistory-diff: report directory renames
Date: Thu, 1 Dec 2016 17:57:05 +0200 [thread overview]
Message-ID: <20161201155705.GA11043@linux.intel.com> (raw)
In-Reply-To: <969465ac-9c0b-81b6-b0a8-69ee69613474@linux.intel.com>
On Tue, Nov 29, 2016 at 03:51:21PM +0200, Alexander Kanavin wrote:
> On 11/28/2016 07:28 PM, Ed Bartosh wrote:
> >The script detects directory renaming if two different
> >directories with the same set of files are added and removed.
>
> What happens if the sets of files are slightly different? (e.g. a
> couple of files are added or removed). Can we get some wiggle space
> here?
>
In this case script will behave like it does currently. It will show all
added and removed files.
--
Regards,
Ed
prev parent reply other threads:[~2016-12-01 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 17:28 [PATCH] buildhistory-diff: report directory renames Ed Bartosh
2016-11-29 13:51 ` Alexander Kanavin
2016-12-01 15:57 ` Ed Bartosh [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=20161201155705.GA11043@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=alexander.kanavin@linux.intel.com \
--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