similar to: Repo for RHEL docs in CentOS Stream

On Fri, 2021-09-17 at 14:19 +0200, Tomas Capek wrote: > Hey folks, > > ??? I'm following up after a meeting with Rich, Karsten, and others, > where we discussed next steps towards setting up a mirror of > > https://gitlab.cee.redhat.com/red-hat-enterprise-linux-documentation/rhel-8-docs > > at > > https://gitlab.com/redhat/centos-stream/docs > >

Hi all, while Option 2 was my favorite as well and it looks great on wide screens, one concern is that it might not look as good on mobile devices. Since we had a sync-up call with Shaun last week, we added Option 4 which shows collapsible docs lists and categories under each major version. Hope that helps, Tomas On Fri, Mar 25, 2022 at 7:52 PM Amy Marrich <amy at redhat.com> wrote:

Hi, I believe the following patch in the GIT - 2.6.17-rc5 is not correct: http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=75616cf9854b83eb83a968b1338ae0ee11c9673c It is the second of the two patches contributed by Leonid Ananiev. This one incorrectly adds the super block unlocking in the error path, though. As we can see in the function ext3_group_add() the

I've only started looking through but I like Option 2. As you said the list will get longer and this will ultimately have less scrolling then having everything listed vertically/ Amy *Amy Marrich* She/Her/Hers Principal Technical Marketing Manager - Cloud Platforms Red Hat, Inc <https://www.redhat.com/> amy at redhat.com Mobile: 954-818-0514 Slack: amarrich IRC: spotz

Hello - Can anyone explain why I get the stack trace in background_server.log when I try to start my first worker? I don''t get this on subsequent workers, only the first one. I should note, the method I am using to start backgroundrb is documented in the archives, and is likely the root of this problem. Suggestions about how to "fix" or avoid this issue are appreciated.

On 11/4/07, bugzilla-daemon at cs.uiuc.edu <bugzilla-daemon at cs.uiuc.edu> wrote: > --- Comment #1 from Chris Lattner <sabre at nondot.org> 2007-11-04 11:45:00 --- > The release notes say "The -cee pass is known to be buggy, and may be removed > in a future release.". I think we should just do it. Oops, I should have read the "known problems" section of

hi there say that i have this table >x<-table(adoc, oarb) >x oarb 0 1 adoc ab 1 0 am 5 1 ba 14 1 cc 271 3 ch 87 2 dz 362 6 fl 7 0 fs 84 2 is there an easy way to get the row names or row

Hi, I'm trying to create two gluster volumes over two nodes with two seperate networks: The names are in the hosts file of each node: root at gluster01 :~# cat /etc/hosts 127.0.0.1 localhost 127.0.1.1 gluster01.peiker-cee.de gluster01 10.0.2.54 gluster02g1.peiker-cee.de gluster02g1 10.0.7.54 gluster02g2.peiker-cee.de gluster02g2 10.0.2.53

Hi there, We're currently having problems mounting share from a windows server 2003 machine. The thing that I find surprising is about smbclient : in fact, I'm allowed to browse the share with the command smbclient : # smbclient //adoc/pastel -U mathus%9g8e Domain=[MIPIH] OS=[Windows Server 2003 3790] Server=[Windows Server 2003 5.2] smb: \> And when I try to mount this share with

Hello all, As the holiday season looms upon us, and NUT cracker sounds can be heard everywhere, I wonder if the current codebase is good enough to cut a 2.8.3 release some time soonish. Active development of recently contributed drivers has somewhat subsided; there are still some planned revisions (notably about documentation and statuses for ECO and similar modes), but some more get shelved

Hello all, As the holiday season looms upon us, and NUT cracker sounds can be heard everywhere, I wonder if the current codebase is good enough to cut a 2.8.3 release some time soonish. Active development of recently contributed drivers has somewhat subsided; there are still some planned revisions (notably about documentation and statuses for ECO and similar modes), but some more get shelved

On Mar 17, 2006, at 12:19 PM, Chris Lattner wrote: > Great. Note that -cee is a beta pass... it has some known bugs and > isn't planned to be worked on in the immediate future. :( After a bit of digging, I found one open bug and two failing test cases, all of which appear to be feature requests: #217: LLVM needs a generic dominator update mechanism nullpointer.ll: "a

Yeah, my issue with Option 2 was that it doesn't reflow. We could get the same side-by-side effect while allowing reflow on smaller screens using CSS flexbox or grid, but I don't know how to do that in asciidoc. Sometimes sites just hand-craft the HTML of the landing page, but I don't want to make work for people. Also, we should consider how well these designs will work with three

I'm starting down the path of testing. There are commits in the rc tag that are not on master: $ git log --oneline ..v2.8.3-rc1 3d286fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle also FTY and fightwarn branches 4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn branches 504706d45 Makefile.am: nut-scanner does directly depend on clients after all

I'm starting down the path of testing. There are commits in the rc tag that are not on master: $ git log --oneline ..v2.8.3-rc1 3d286fb1b (tag: v2.8.3-rc1, jimklimov/pre-283-2) appveyor.yml: handle also FTY and fightwarn branches 4e92275c1 .github/workflows/codeql.yml: handle also FTY and fightwarn branches 504706d45 Makefile.am: nut-scanner does directly depend on clients after all

On Fri, 17 Mar 2006, Eric Kidd wrote: >> I'm particularly confused by the rlwinm instructions that keep turning up >> in PowerPC output, and the double test against 98. I don't have a problem >> or anything; I'm just trying to figure out what's going on. :-) > > Ah! The backend is running -lowerswitch, which does a binary search of the > case labels

Sorry, that was one mishap layered onto another - the "v2.8.3-rc1" tag was supposed to point to the same commit as what I originally hoped was "v2.8.3"... but did not - instead initially pointed to what would land to `master` among its fixes for a cleaner release. Hopefully tags are correctly refined on GitHub repo now, at least. Jim On Tue, Apr 8, 2025 at 2:58?PM Greg

Sorry, that was one mishap layered onto another - the "v2.8.3-rc1" tag was supposed to point to the same commit as what I originally hoped was "v2.8.3"... but did not - instead initially pointed to what would land to `master` among its fixes for a cleaner release. Hopefully tags are correctly refined on GitHub repo now, at least. Jim On Tue, Apr 8, 2025 at 2:58?PM Greg

Hi Samba team and Maxence, > last week we updated three domain controllers (Sernet Samba) from 4.2 to > 4.7, typical upgrade path (4.3->4.4->4.5->4.6->4.7), everything was ok. > > The next day we got a mail from the Sernet team informing they fixed a > bug affecting the group memberships. > > https://bugzilla.samba.org/show_bug.cgi?id=13095 > > We've

Hi all, Pursuant to http://llvm.org/bugs/show_bug.cgi?id=1769 , I'm going to remove the CEE pass, which includes the Transforms/Scalar/ CorrelatedExprs.cpp file. If anyone has any objections to removing this pass and/or file, please speak now. Thanks! -bw