From: jim owens <jowens@hp.com>
To: Lee Trager <lt73@cs.drexel.edu>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Status of btrfs-unstable-standalone?
Date: Wed, 11 Feb 2009 14:17:47 -0500 [thread overview]
Message-ID: <4993245B.30707@hp.com> (raw)
In-Reply-To: <20090211170950.GA19251@tux64-01>
Lee Trager wrote:
> I've noticed that the btrfs-unstable-standalone repository hasn't been
> updated in over three weeks. It seems all active development is taking
> place on btrfs-unstable. What is happening to the
> btfs-unstable-standalone repository? Will all future development only be
> on btrfs-unstable or is there some other reason
> btrfs-unstable-standalone hasn't been updated?
Chris was having a problem with the scripts to make the
standalone from the main tree. All submits go to the
main tree first. I'm sure the only reason the standalone
is not being updated is that Chris has not had time to
fix the scripts. Someone else who knows git and scripting
might be able to do that for him.
jim
prev parent reply other threads:[~2009-02-11 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 17:09 Status of btrfs-unstable-standalone? Lee Trager
2009-02-11 19:17 ` jim owens [this message]
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=4993245B.30707@hp.com \
--to=jowens@hp.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lt73@cs.drexel.edu \
/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