Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1636482 > unrolled thread
| Started by | Bob Peterson <rpeterso@redhat.com> |
|---|---|
| First post | 2017-05-05 18:40 +0200 |
| Last post | 2017-05-05 18:40 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Regression in my latest GFS2 pull request Bob Peterson <rpeterso@redhat.com> - 2017-05-05 18:40 +0200
| From | Bob Peterson <rpeterso@redhat.com> |
|---|---|
| Date | 2017-05-05 18:40 +0200 |
| Subject | Regression in my latest GFS2 pull request |
| Message-ID | <tDOqR-4ap-7@gated-at.bofh.it> |
Hi Linus, I see that you haven't processed my latest GFS2 pull request. Today I found a regression in one of those patches. I've written, tested, and posted a patch to cluster-devel to fix the problem, and I'd like to get it into this merge window because it's severe. (You can't unmount a gfs2 file system after withdraw due to errors). My question is: How would you like me to handle it? Push the new patch, tag it, and do a second pull request? Wait until you've processed the first pull request, then do so? Or is there a better way? Regards, Bob Peterson
Back to top | Article view | linux.kernel
csiph-web