From: Kip Macy <kip.macy@gmail.com>
To: Paul Larson <plars@linuxtestproject.org>
Cc: xen-devel <xen-devel@lists.xensource.com>, kmacy@fsmware.com
Subject: Re: make mkpatches broken
Date: Tue, 19 Apr 2005 11:51:22 -0700 [thread overview]
Message-ID: <b1fa29170504191151e053c34@mail.gmail.com> (raw)
In-Reply-To: <1113935923.6127.97.camel@localhost.localdomain>
FreeBSD isn't setup as a default target so I didn't stick anything in to tie in.
Is there something I should add to play nicely with others?
On 4/19/05, Paul Larson <plars@linuxtestproject.org> wrote:
> I just noticed that make mkpatches seems to be broken in at least
> xen-unstable at the moment. Complains about not having a target for
> freebsd since it picks it up in ALLSPARSETREES, but no mk file exists
> for it under buildconfigs. I'm guessing something probably just got
> dropped when Kips freebsd stuff was merged?
>
> On a related note, the whole bug tracking system thread seems to have
> fizzled with what seemed, from what I saw at least, everyone agreeing
> that a bug tracking system would be nice to have, and "the sooner the
> better." Is there a more concrete date by which we can believe the bug
> tracking system will be available for everyone to use?
>
> --
> Thanks,
> Paul Larson
> plars@linuxtestproject.org
> http://www.linuxtestproject.org
>
>
>
next prev parent reply other threads:[~2005-04-19 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 18:38 make mkpatches broken Paul Larson
2005-04-19 18:51 ` Kip Macy [this message]
2005-04-19 19:10 ` Paul Larson
-- strict thread matches above, loose matches on Subject: below --
2005-04-19 22:25 Ian Pratt
2005-04-19 23:37 ` Nivedita Singhvi
2005-04-19 23:56 Ian Pratt
2005-04-20 0:05 ` Jeremy Katz
2005-04-20 0:14 ` Nivedita Singhvi
2005-04-20 0:21 ` Nivedita Singhvi
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=b1fa29170504191151e053c34@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=kmacy@fsmware.com \
--cc=plars@linuxtestproject.org \
--cc=xen-devel@lists.xensource.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.