From: Jonathan Liu <net147@gmail.com>
To: Jonathan Liu <net147@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] buildhistory: record removals with Git 2.0 and later
Date: Fri, 31 May 2013 20:29:19 +1000 [thread overview]
Message-ID: <51A87B7F.7050702@gmail.com> (raw)
In-Reply-To: <1369993335-21441-1-git-send-email-net147@gmail.com>
On 31/05/2013 7:42 PM, Jonathan Liu wrote:
> There is a behavior change with Git 2.0 where "git add ." will no
> longer record removals by default unless -A (--all) is specified.
> Change to "git add -A ." so removals are recorded with Git 2.0 and
> later.
>
> Signed-off-by: Jonathan Liu <net147@gmail.com>
> ---
> meta/classes/buildhistory.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Hmm... looks like I interpreted the Git warning incorrectly. Maybe I
need to look into this a bit more and perhaps change the commit message.
The following appears after a build with buildhistory enabled:
warning: You ran 'git add' with neither '-A (--all)' or '--ignore-removal',
whose behaviour will change in Git 2.0 with respect to paths you removed.
Paths like 'test.txt' that are
removed from your working tree are ignored with this version of Git.
* 'git add --ignore-removal <pathspec>', which is the current default,
ignores paths you removed from your working tree.
* 'git add --all <pathspec>' will let you also record the removals.
Run 'git status' to check the paths you removed from your working tree.
Regards,
Jonathan
next prev parent reply other threads:[~2013-05-31 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 9:42 [PATCH] buildhistory: record removals with Git 2.0 and later Jonathan Liu
2013-05-31 10:29 ` Jonathan Liu [this message]
2013-05-31 10:31 ` Jonathan Liu
2013-05-31 10:42 ` Paul Eggleton
2013-05-31 10:50 ` Paul Eggleton
2013-05-31 10:52 ` Jonathan Liu
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=51A87B7F.7050702@gmail.com \
--to=net147@gmail.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 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.