From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Loss of all package history following the recipe rename.
Date: Wed, 18 Mar 2009 13:56:19 -0400 [thread overview]
Message-ID: <49C135C3.9040206@balister.org> (raw)
In-Reply-To: <b6ebd0a50903180906v755f082akf8460a3b3307d9fd@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
Chris Larson wrote:
> On Wed, Mar 18, 2009 at 8:38 AM, John Willis
> <John.Willis@distant-earth.com> wrote:
>> <snip>
>>
>> After kergoth took the time to point out that I was just looking at this
>> 'the wrong way' and not 'the GIT way' I think the mail can safely be
>> disregarded ;-).
>>
>> It still does not change the fact that the behavior of 'git log' gave me a
>> real panic moment but at least nothing is lost if your happy to dig (or
>> rather use git log --follow, ok, next time I promise to read the man page
>> before panicking ;-), I am just used to --follow functionality being a
>> default behavior).
>
> Re: default behavior, I'm not entirely certain, but the 'diff.renames'
> git config parameter seems promising. Try running:
> git config diff.renames true
>
> I'm not sure if git log --follow is the same thing as git diff-tree
> -M, but it probably is, since git log is essentially git rev-list |
> git diff-tree.
A friend of mine pointed me at this article:
http://markmail.org/message/x7ubgl6wanubwa3g#query:git%20mv%20lost%20history+page:1+mid:pl3pbiuhzu2excg7+state:results
Hopefully, this makes more send to the git gurus.
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2009-03-18 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <-2193387358217288963@unknownmsgid>
2009-03-18 16:06 ` Loss of all package history following the recipe rename Chris Larson
2009-03-18 17:56 ` Philip Balister [this message]
2009-03-18 18:07 ` Chris Larson
[not found] <27612.658069893$1237390186@news.gmane.org>
2009-03-18 15:52 ` Koen Kooi
2009-03-18 15:23 John Willis
2009-03-18 15:38 ` John Willis
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=49C135C3.9040206@balister.org \
--to=philip@balister.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox