Re: [PATCH xfsprogs] build: don't assume $BUILD_CC has fsmap.h just because $CC does

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 9/21/18 2:34 PM, Brian Norris wrote:
> On Fri, Sep 21, 2018 at 02:12:31PM -0500, Eric Sandeen wrote:
>> On 9/21/18 1:37 PM, Brian Norris wrote:
>>> Ping? Should I send a new version that combines our patches?
>>
>> Hi Brian - I'm not ignoring your patch, I've just been working on getting
>> libxfs synced for 4.19 before merging anything else - this is usually how
>> I work when patches come in near the beginning of a release cycle.
>> I'll revisit your patch & reach out to you if I have other questions or
>> suggestions when I get there, ok?  Sorry for the delay.
> 
> No problem at all. I don't think I understood the development patterns
> here anyway. It just wasn't clear if there was a next action for me.
> This makes it clear.

Eh, it changes from time to time and isn't exactly advertised, no worries.

And this time I'm a bit behind so xfsprogs is as well.

Normal xfsprogs cycle lately is something like:

Release the last version to match the last kernel, shortly after last kernel release
Start merging in libxfs changes from next devel kernel to prepare for next release, cut -rc0
Pick up most of the accumulated pending patches, cut an -rc1
do the normal soak/patch collection until release, rc's as needed
rinse, repeat.

-Eric



[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux