All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: McClintock Matthew-B29882 <B29882@freescale.com>,
	openembedded-devel@lists.openembedded.org
Subject: Re: [meta-webserver][PATCH 0/6] Add meta-webserver
Date: Wed, 03 Oct 2012 15:18:33 +0100	[thread overview]
Message-ID: <2524595.q9KP7Ea2Q1@helios> (raw)
In-Reply-To: <70CC66F5C30A414DADDA6973E4CA391A6CBF8D@039-SN1MPN1-001.039d.mgd.msft.net>

On Wednesday 03 October 2012 14:08:16 McClintock Matthew-B29882 wrote:
> On Wed, Oct 3, 2012 at 8:43 AM, Paul Eggleton
> 
> <paul.eggleton@linux.intel.com> wrote:
> > The answer is no, it doesn't.
> > 
> > I guess on reflection we probably ought to be consistent here though - for
> > better or worse, this is not what has been done when pulling in recipes
> > from OE-Classic for the rest of meta-openembedded. The commit message
> > does already list the changes from the original, and I'll concede that
> > having just one revision doesn't give a huge amount in the way of insight
> > on previous origin; ultimately as you say, OE-Classic is still there as a
> > reference for that.
> > 
> > OK, I've squashed those commits out on the branch. Would it be worth me
> > posting a v2 after all these changes?
> 
> Actually, this is one really annoying thing about OE. When people
> rename the file 'git blame' comes worthless. Is there a way around
> this?

Usually it picks up on renames just fine, but as with git diff -M there is some 
fuzziness in how it determines the difference between a file rename and an 
unrelated delete followed by an add; sometimes the difference is too great for 
git to consider as a rename with its default settings. I just tested, you can 
improve rename detection with git blame by using the -C option though; 
adjusting the -M value might also help.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



  reply	other threads:[~2012-10-03 14:31 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-01 16:14 [meta-webserver][PATCH 0/6] Add meta-webserver Paul Eggleton
2012-10-01 16:14 ` [meta-webserver][PATCH 1/6] Add meta-webserver layer Paul Eggleton
2012-10-01 16:14 ` [meta-webserver][PATCH 2/6] apache2: add from OE-Classic Paul Eggleton
2012-10-03 10:17   ` Koen Kooi
2012-10-03 11:28     ` Paul Eggleton
2012-10-03 11:41       ` Koen Kooi
2012-10-03 12:23         ` Paul Eggleton
2012-10-01 16:14 ` [meta-webserver][PATCH 3/6] modphp: " Paul Eggleton
2012-10-03 10:20   ` Koen Kooi
2012-10-03 11:28     ` Paul Eggleton
2012-10-03 11:44       ` Koen Kooi
2012-10-01 16:14 ` [meta-webserver][PATCH 4/6] apache2: update to version 2.4.2 and fix Paul Eggleton
2012-10-01 16:14 ` [meta-webserver][PATCH 5/6] modphp: update to 5.3.14 " Paul Eggleton
2012-10-01 16:14 ` [meta-webserver][PATCH 6/6] xdebug: add new recipe Paul Eggleton
2012-10-03 10:21   ` Koen Kooi
2012-10-03 11:28     ` Paul Eggleton
2012-10-03 11:47       ` Koen Kooi
2012-10-03 13:08         ` Paul Eggleton
2012-10-02 14:40 ` [meta-webserver][PATCH 0/6] Add meta-webserver Koen Kooi
2012-10-02 14:53   ` Paul Eggleton
2012-10-03 10:24 ` Koen Kooi
2012-10-03 10:43   ` Paul Eggleton
2012-10-03 11:27     ` Koen Kooi
2012-10-03 11:29       ` Paul Eggleton
2012-10-03 11:43         ` Koen Kooi
2012-10-03 12:23           ` Paul Eggleton
2012-10-03 13:12             ` Koen Kooi
2012-10-03 13:43               ` Paul Eggleton
2012-10-03 14:08                 ` McClintock Matthew-B29882
2012-10-03 14:18                   ` Paul Eggleton [this message]
2012-10-03 14:19                   ` Khem Raj

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=2524595.q9KP7Ea2Q1@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=B29882@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.