* Status of btrfs-unstable-standalone?
@ 2009-02-11 17:09 Lee Trager
2009-02-11 19:17 ` jim owens
0 siblings, 1 reply; 2+ messages in thread
From: Lee Trager @ 2009-02-11 17:09 UTC (permalink / raw)
To: linux-btrfs
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?
Thanks,
Lee
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Status of btrfs-unstable-standalone?
2009-02-11 17:09 Status of btrfs-unstable-standalone? Lee Trager
@ 2009-02-11 19:17 ` jim owens
0 siblings, 0 replies; 2+ messages in thread
From: jim owens @ 2009-02-11 19:17 UTC (permalink / raw)
To: Lee Trager; +Cc: linux-btrfs
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-02-11 19:17 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-02-11 17:09 Status of btrfs-unstable-standalone? Lee Trager
2009-02-11 19:17 ` jim owens
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox