All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@openembedded.org
Subject: Re: fatal: Not a git repository
Date: Mon, 02 Mar 2009 19:28:49 -0600	[thread overview]
Message-ID: <49AC87D1.3050505@dls.net> (raw)
In-Reply-To: <49AB58CA.7090406@tait.co.nz>

Douglas Royds wrote:
> Anyone else getting this?
> 
>    NOTE: Handling BitBake files: / (6587/6587) [100 %]
>    NOTE: Parsing finished. 6302 cached, 0 parsed, 285 skipped, 0 masked.
>    NOTE: Cache is clean, not saving.
>    NOTE: build 200903021645: started
>    fatal: Not a git repository <----------------------
> 
>    OE Build Configuration:
>    BB_VERSION        = "1.8.12"
>    ...
> 
> The same complaint seems to crop up at various points during a build, as
> well.

Yes, I see that as well.  Of course, since I -- at the time -- was
building from a snapshot and not the original git repo, and the build
results seemed quite normal, I gave it no further thought.


> =======================================================================
> This email, including any attachments, is only for the intended
> addressee.  It is subject to copyright, is confidential and may be
> the subject of legal or other privilege, none of which is waived or
> lost by reason of this transmission.
> If the receiver is not the intended addressee, please accept our
> apologies, notify us by return, delete all copies and perform no
> other act on the email.
> Unfortunately, we cannot warrant that the email has not been
> altered or corrupted during transmission.
> =======================================================================

I guess I'm not sure that I am the intended addressee.  Can you tell me
if you did, in fact, intend to send the original email to me, in the
legal sense of the definition of "intended addressee"?

In any case, please inform your legal department that I do not accept
apologies from lawyers, and that this email constitutes my notification
of that to your lawyers, that I have deleted all copies -- at least
those copies that _I_ possess; the email notice is rather vague as to
whether I am required to track down all copies that might exist in the
world today -- and I also shall perform no other act on the email.

- Mike (mwester)

P.S.  Neither can I warrant that my response to this email has not been
altered or corrupted during transmission.  And I'll go one better than
your lawyers, and note that you'll never know if my original email was
full of typos -- and that it was actually *corrected* during
transmission.  Poor lawyers...  that sort of disclaimer rather makes the
entire footnote they added there completely ridiculous and pointless,
doesn't it??!



  parent reply	other threads:[~2009-03-03  1:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02  3:55 fatal: Not a git repository Douglas Royds
2009-03-03  0:12 ` Vitus Jensen
2009-03-03  2:17   ` Tom Rini
2009-03-03  5:54     ` Douglas Royds
2009-03-03  8:14       ` pHilipp Zabel
2009-03-03  1:28 ` Mike (mwester) [this message]
2009-03-03  8:45   ` Yuri Bushmelev
  -- strict thread matches above, loose matches on Subject: below --
2011-10-14  1:57 T
2011-10-14  2:14 ` BlackSwan

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=49AC87D1.3050505@dls.net \
    --to=mwester@dls.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.