All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter A. Bigot" <pab@pabigot.com>
To: "Burton, Ross" <ross.burton@intel.com>,
	 Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [oe] Style issue for recipes
Date: Thu, 04 Sep 2014 11:44:40 -0500	[thread overview]
Message-ID: <540896F8.9040805@pabigot.com> (raw)
In-Reply-To: <CAJTo0LbNG14cHQN8JewwOd-Z0rBOeSpEQKHOQguSQweiQzLVtQ@mail.gmail.com>

On 09/04/2014 11:29 AM, Burton, Ross wrote:
> On 4 September 2014 17:07, Enrico Scholz
> <enrico.scholz@sigma-chemnitz.de> wrote:
>> .inc files make sense with current packaging because they are revision
>> control friendly.  E.g. you can put the logic into .inc and follow its
>> history with 'git log' which is not possible when there are only the
>> versioned .bb files.
> You can follow changes to the .inc but not anything that went in and
> out of the .bb, but I do concede that git not tracking the renames
> directly does mean some histories are harder to track (although simple
> to follow as the commit where the history stops will tell you where to
> pick it up again).

git log --follow foo_1.2.bb handles 90% of this:

       --follow
            Continue listing the history of a file beyond renames (works 
only for a single file).

E.g. you can go all the way back to systemd 196 with:

     git log --follow meta/recipes-core/systemd/systemd_216.bb

Peter


  reply	other threads:[~2014-09-04 16:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 14:12 Style issue for recipes Burton, Ross
2014-09-04 15:03 ` [oe] " Robert Yang
2014-09-04 15:03   ` Robert Yang
2014-09-04 15:29   ` Peter A. Bigot
2014-09-04 15:41   ` [oe] " akuster808
2014-09-04 15:41     ` [OE-core] " akuster808
2014-09-04 16:26     ` [oe] " Burton, Ross
2014-09-04 16:26       ` [OE-core] " Burton, Ross
2014-09-04 20:03       ` [oe] " akuster808
2014-09-04 20:03         ` [OE-core] " akuster808
2014-09-04 16:07 ` [oe] " Enrico Scholz
2014-09-04 16:29   ` Burton, Ross
2014-09-04 16:44     ` Peter A. Bigot [this message]
2014-09-04 17:00       ` Enrico Scholz
2014-09-04 17:38         ` Andreas Müller
2014-09-04 18:36           ` Enrico Scholz
2014-09-04 19:12             ` Burton, Ross
2014-09-29  0:51               ` Trevor Woerner
2014-09-04 16:34 ` Burton, Ross
2014-09-04 17:29   ` Andreas Müller
2014-09-04 17:54     ` Philip Balister
2014-09-04 19:10       ` Burton, Ross
2014-09-05 13:58     ` Mike Looijmans
2014-09-05 16:13       ` Burton, Ross
2014-09-05  9:11 ` [oe] " Paul Eggleton
2014-09-05  9:11   ` Paul Eggleton

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=540896F8.9040805@pabigot.com \
    --to=pab@pabigot.com \
    --cc=enrico.scholz@sigma-chemnitz.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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.