I haven't received any requests from anyone, so I haven't made any progress
here! This is what my quick look at the commits indicated. I added git
notes to these commits in my github account repo if you want to check. Here
is the list, let me know if you need any additions or removals. I haven't
attempted any merges yet, so I may add some trivial commits to this list to
make 'cherry-pick' happy!
$ git notes --ref=backport list | awk '{print $2}' | xargs -n1 git log -1
--oneline
09303d9b1 FSAL_PROXY : storing stateid from background NFS server
09c74126a nfs: fix error handling in layoutrecall code
0d045c355 GPFS_FSAL : Collect and extract performance stats
14250b586 Fixup request_mask handling in mdcache_refresh_attrs
32c723a0c [GPFS] read_dirents: check status of FD gathering instead of FD
itself.
40ee79dbf packaging (rpm): /var/log/ganesha has incorrect owner (selinux)
42abee8a1 Fix Dispatch_Max_Reqs max value in documentation.
55b5fc62c FSAL_GLUSTER: Free glfs object in case of export creation failures
57c9c3032 Fix open_for_locks parameter in gpfs_lock_op2
698ce898b Fix rpc-statd.service path on debian
7934673a5 Create v4.1+ openowner with confirmed flag already set
7d0629b3b Fix dec_client_record_ref accessing freed memory
7f95da09b [GPFS] return first failure from gpfs_read2 and gpfs_write2
85bd9217d GLUSTER: make sure to free xstat when meeting error
8b67807c5 Use 'v6disabled' flag to know if IPv6 is disabled
8e7b14d75 [GPFS] Removed get_my_fd()
9fbb6bc1a [GPFS] remove duplicate code in find_fd()
a5d2eb13b make the LIBEXECDIR valid for distro Debian or Ubuntu
a5fc5c1ad setclientid: free clientid if client_r_addr is too long.
a635a4b1f FSAL_PROXY : manage clean close of PROXY threads
c0f2d9f31 nfs: nfs_rpc_get_chan must hold cid_mutex to walk sessions list
ca2a2143c FSAL_RGW depends on FSAL status method that it doesn't implement
cca16acb7 FSAL_PROXY : preserving request_mask in getattrs
ce56e157e Remove nfs_rpc_dispatch_stop
d7f1dc1ef GPFS_FSAL : Rectification of perf stats code
d89d67db2 nfs: fix error handling in nfs_rpc_v41_single
deccd5613 FSAL_GLUSTER: detach export in case of failures
e5db2a83d Fix sleep path for debian
f48772730 Fix to make sure op_ctx is set when calling mdcache_lru_unref().
f4e18dddf DBus: Shutdown dbus thread before closing the connection
f527e489c Allow cancellation of upcall threads even if not ready
f7b76ea1b Use state_lock to prevent race between FREE_STATEID and LOCK/new
lock owner
fea84d795 [GPFS] Check find_fd() return status in gpfs_lock_op2
On Thu, Oct 5, 2017 at 3:09 AM, Frank Filz <ffilz...@mindspring.com> wrote:
> When we first talked about stable maintenance for V2.5, it seemed like IBM
> was most likely to be using V2.5 and we elected Malahal to be V2.5-stable
> maintainer.
>
> It now seems we have pressure from other fronts for V2.5 stable fixes, I'd
> like to open the discussion on how best to manage it? I'd be happy to do
> additional backports and V2.5-stable tagging, or we could ask Kaleb to do
> it, or we can operate on a "make requests to Malahal" procedure.
>
> Any input here is welcome, I want to make sure we respect everyone's needs
> for V2.5-stable.
>
> Frank
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Nfs-ganesha-devel mailing list
> Nfs-ganesha-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nfs-ganesha-devel mailing list
Nfs-ganesha-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
