On Tue, May 10, 2022 at 9:27 PM Ryosuke Niwa <rniwa@webkit.org> wrote:
On Tue, May 10, 2022 at 20:36 Chris Dumez <cdumez@apple.com> wrote:
[Not sure why Apple Mail sent Ryosuke’s replies to the Junk folder but I finally noticed.]
It's something to do with @webkit.org not being able to send a proper sender ID due to it being a forwarding address.
On May 10, 2022, at 3:04 PM, Ryosuke Niwa via webkit-dev <webkit-dev@lists.webkit.org> wrote:
On Tue, May 10, 2022 at 3:01 PM Jonathan Bedard via webkit-dev <webkit-dev@lists.webkit.org> wrote:
On May 10, 2022, at 2:46 PM, Geoffrey Garen <ggaren@apple.com> wrote:
Do I undertand correctly that the proposal here is
(a) Immediately Deprecate ChangeLogs
Yes
(b) Immediately end support for posting patches from Subversion checkouts?
We would be immediately ending support for _landing_ patches posted from a Subversion checkout. EWS would continue to accept and test patches posted from Subversion checkouts.
Just this week, I landed 2~3 patches using a pure Subversion checkout. It's actually my primary method of landing patches in WebKit right now.
Do you feel like 1 week is not enough time for you to do a git checkout and familiarize yourself enough with GIT to upload patches? Is that the issue? If so, how long do you feel would be reasonable?
I already have GitHub clones. The issue I have is with committing directly. I need to be able to commit directly as is since commit queue even fast one is simply way too slow.
If you’re not ready to adopt the GitHub workflow for a reason or another, git-svn / bugzilla patches is still a thing and will still work for now. Only committing from pure SVN repositories would go away in a week.
Well, that's precisely my use case. I don't even write a patch in a pure Subversion checkout anymore these days.
- R. Niwa
-- - R. Niwa