From: Richard Purdie <rpurdie@linux.intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: inc files in recipes
Date: Fri, 19 Nov 2010 12:02:26 +0000 [thread overview]
Message-ID: <1290168146.1272.12237.camel@rex> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1504D3667EC1C@shsmsx502.ccr.corp.intel.com>
On Fri, 2010-11-19 at 17:47 +0800, Tian, Kevin wrote:
> >From: Frans Meulenbroeks [mailto:fransmeulenbroeks@gmail.com]
> >Sent: Friday, November 19, 2010 5:43 PM
> >
> >>
> >>>
> >>>Here the inc file could be merged into the bb file.
> >>>This has the advantage of having only a single file, so it is slightly
> >>>easier if you want to read or maintain the recipe.
> >>
> >> One advantage of not doing so is to retrieve change history in git easily.
> >> Version change on .bb is a rename which in git is simply a remove and
> >> create, while with .inc you can easily track history. This also reduces the
> >> commit size.
> >
> >If I am correct git mv does preserve history although the name change
> >makes it a little bit more difficult to track them.
>
> I'm not sure how that works consistently. Sometimes the rename is kept
> while most times it doesn't happen to me. :-(
Git does not track renames. Some of its tools can however detect renames
which is subtly different. See "git diff -M" which detects renames for
example.
Cheers,
Richard
next prev parent reply other threads:[~2010-11-19 12:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 8:44 inc files in recipes Frans Meulenbroeks
2010-11-19 8:55 ` Gary Thomas
2010-11-19 9:24 ` Frans Meulenbroeks
2010-11-19 9:20 ` Tian, Kevin
2010-11-19 9:42 ` Frans Meulenbroeks
2010-11-19 9:47 ` Tian, Kevin
2010-11-19 12:02 ` Richard Purdie [this message]
2010-11-19 12:05 ` Richard Purdie
2010-11-19 12:25 ` Frans Meulenbroeks
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=1290168146.1272.12237.camel@rex \
--to=rpurdie@linux.intel.com \
--cc=kevin.tian@intel.com \
--cc=yocto@yoctoproject.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.