Hi there! Thanks for the clarification, and apologies for the delay. Below are the 5-digit change numbers from Gerrit that we'd need to pull up to a stable branch in order to fully support AIX:
15107 15116 15110 15112 15113 15114 15108 15119 15118 15122 15144 15145 15143 15146 15142 15310 15311 15312 Is there anything I can help do to get those incorporated into the next release? Thank you so much! -Ben ________________________________ From: Benjamin Kaduk <ka...@mit.edu> Sent: Saturday, March 4, 2023 6:37 PM To: Ben Huntsman <b...@huntsmans.net> Cc: Stephan Wiesand <stephan.wies...@desy.de>; openafs-devel@openafs.org <openafs-devel@openafs.org> Subject: Re: [OpenAFS-devel] Pulling up changes to stable The change number would be the 5-digit number from gerrit, but any of those would work well enough to identify what you want. -Ben On Fri, Mar 03, 2023 at 11:36:47PM +0000, Ben Huntsman wrote: > Hi Stephan! > Thank you for the reply! I am happy to provide that information. To be > clear, what are you looking for when you say "change numbers"? The 5-digit > number from Gerrit? The Change-ID hash from the commit? Or the sha of the > commit to master itself? > > Thank you again! > > -Ben > > ________________________________ > From: Stephan Wiesand <stephan.wies...@desy.de> > Sent: Friday, March 3, 2023 10:12 AM > To: Ben Huntsman <b...@huntsmans.net> > Cc: openafs-devel@openafs.org <openafs-devel@openafs.org> > Subject: Re: [OpenAFS-devel] Pulling up changes to stable > > Hi Ben, > > > On 3. Mar 2023, at 18:13, Ben Huntsman <b...@huntsmans.net> wrote: > > > > Hi there! > > Thank you for accepting the patches I submitted to get OpenAFS working > > on AIX 7.2-7.3, as well as the previous ones! > > thank you for whipping those up. > > > Now that they're all there in the master branch, what needs to be done > > to pull them up into an upcoming stable branch? > > These changes are on my list of things I want to get into stable. I'm just > slow. > > > I read the GitDevelopers page, but is it ok for anyone to push patches to > > Gerrit for an upcoming stable, or is there some additional review process? > > In principle it's ok, provided that those patches are clean cherry-picks from > master. In practice, it causes extra work if a change pulled up like this > touches a file already modified by any other change in the queue. In > addition, you'll sometimes (or rather often) find that the change from master > doesn't apply cleanly to stable, and either needs to be modified or > (preferrably) be supplemented by more changes from master not yet on stable. > > Mind you, you're absolutely free to submit those pull-ups yourself. The most > appreciated way you can help though is to provide a list of change numbers > you'd like to see in an upcoming stable release. And keep poking... > > Best regards, > Stephan > > > > > Thank you much! > > > > -Ben > > > -- > Stephan Wiesand > DESY - DV - > Platanenallee 6 > 15738 Zeuthen, Germany > > >
