On 10/08/2017 02:09 AM, Malahal Naineni wrote:
Soumya, Added that commit in addition to what I posted. I tried merging
all 34 commits but couple things failed, so I bailed out the following.
If you need any of these, please let me know!
Thanks Malahal..Thats fine by me.
-Soumya
1) 09303
Soumya, Added that commit in addition to what I posted. I tried merging all
34 commits but couple things failed, so I bailed out the following. If you
need any of these, please let me know!
1) 09303d9b1 FSAL_PROXY : storing stateid from background NFS server
Merge was successful, but compilati
On 10/6/17 9:50 AM, Frank Filz wrote:
But if we can build a script that would easily show which patches have or have
not been backported, that would be a big help. Right now, I’m always so
confused as to what has actually been backported…
OR we could shot backporting so much, and release new
From: Malahal Naineni [mailto:mala...@gmail.com]
Sent: Thursday, October 5, 2017 11:58 PM
To: Frank Filz
Cc: nfs-ganesha-devel@lists.sourceforge.net
Subject: Re: [Nfs-ganesha-devel] V2.5-stable maintenance
I use "git log --grep=" to get all commits and then use "git
branch
gt; *Sent:* Wednesday, October 4, 2017 8:52 PM
> *To:* Frank Filz
> *Cc:* nfs-ganesha-devel@lists.sourceforge.net
> *Subject:* Re: [Nfs-ganesha-devel] V2.5-stable maintenance
>
>
>
> It would be nice to "tag" commits that we want to back port with git notes
> or some
a
given fix was backported or not…
Frank
From: Malahal Naineni [mailto:mala...@gmail.com]
Sent: Wednesday, October 4, 2017 8:52 PM
To: Frank Filz
Cc: nfs-ganesha-devel@lists.sourceforge.net
Subject: Re: [Nfs-ganesha-devel] V2.5-stable maintenance
It would be nice to "tag" co
Hi Malahal,
On 10/05/2017 09:06 AM, Malahal Naineni wrote:
85bd9217d GLUSTER: make sure to free xstat when meeting error
Before applying the above patch, I request to backport below commit as
well -
39119aa FSAL_GLUSTER: Use glfs_xreaddirplus_r for readdir
Thanks,
Soumya
It would be nice to "tag" commits that we want to back port with git notes
or some such thing.
Last week's V2.6 commits that need backporting will be ported this week (a
week behind in time to allow some testing in V2.6)
Whoever is going to tag the release can "cherry-pick" the commits (any
merge
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
at
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 h
10 matches
Mail list logo
