From: "John Willis" <John.Willis@Distant-earth.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: Loss of all package history following the recipe rename.
Date: Wed, 18 Mar 2009 15:38:15 -0000 [thread overview]
Message-ID: <01c801c9a7df$8eee7e70$accb7b50$@Willis@Distant-earth.com> (raw)
In-Reply-To: <01c401c9a7dd$8a20b4a0$9e621de0$@Willis@Distant-earth.com>
<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).
Regards,
John
next prev parent reply other threads:[~2009-03-18 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 15:23 Loss of all package history following the recipe rename John Willis
2009-03-18 15:38 ` John Willis [this message]
[not found] <27612.658069893$1237390186@news.gmane.org>
2009-03-18 15:52 ` Koen Kooi
[not found] <-2193387358217288963@unknownmsgid>
2009-03-18 16:06 ` Chris Larson
2009-03-18 17:56 ` Philip Balister
2009-03-18 18:07 ` Chris Larson
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='01c801c9a7df$8eee7e70$accb7b50$@Willis@Distant-earth.com' \
--to=john.willis@distant-earth.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox