Hello everyone,
The scsi subsystem has moved to a single tree model. I'm trying to
keep up with how that tree is managed and as a result I'm going to go to
a single tree model for the kernel patches I mail up to linux-scsi.
I removed the fcoe-next.git, fcoe-fixes.git and fcoe-post-merge.git
repositories and I've created a new linux-fcoe.git tree. All code that
was in fcoe-next.git and/or fcoe-fixes.git has merged upstream so
removing those trees was fine. I have a 'features' branch in
linux-fcoe.git for new patches targeted for the next merge window and
I'll create fix topic branches as needed.
I've been using this model for a kernel cycle already and although
we haven't have many patches lately it seemed to work out well.
Please let me know if you run into any problems with this new
tree/model.
Thanks, //Rob
_______________________________________________
devel mailing list
[email protected]
https://lists.open-fcoe.org/mailman/listinfo/devel
