Re: ACNA20 and Apache https's 25th anniversary
I've added httpd to https://docs.google.com/spreadsheets/d/1W8DEs0nr1SUTlyTo9dj6SG0u2tFSwvRhoDVb9vYb_r0/edit#gid=0 for a tentative one day. If you think we can fill more than one room-day, please speak up. I could presumably do a mod_rewrite talk, although I am sure I need to bring my knowledge up to date a little. I'd love to see a bunch of new/first-time speakers from the younger generation of httpd developers. On 10/6/19 9:24 AM, Jim Jagielski wrote: > Next year will be httpd's 25th anniversary. I think it would be great if the > web server PMC would commit to having a httpd track at ACNA20... > > Anyone else interested? We'd need about 6-7 talks to fill the track. > -- Rich Bowen rbo...@rcbowen.com
Re: Migrate to git?
On Tue, Oct 15, 2019 at 1:42 AM Ruediger Pluem wrote: >... > Would we lose this possibility [of editing log messages] with git? > Yes. The log message is part of the commit hash. You can effectively delete the "tip" commit of a line-of-development, and replace it with a new commit (ie. same code changes, but edited log msg). That new commit would have a different hash. If people sync'd the old commit/hash, their clones are basically broken post-edit. It is effectively impossible to edit a log message if it is not-tip. That is because each ongoing commit has a "parent [hash]" incorporated into its hash signature. So if you go back in time to edit C1, then you're gonna to regenerate hashes for C2, C3, and C4 that came after it. With the corresponding breakage of clones. Arguments can be made for whether this is pro/con, but I think is not worth discussing here. HTH, -g
Re: Migrate to git?
On 10/06/2019 05:06 AM, Daniel Gruno wrote: > There is also, as you mention, the risk of force-pushing to rewrite history, > but as I understand it, we can disable this > by requiring PRs for each change to the canonical branch(es). Maybe a git dummy question, but how do you adjust log messages for already pushed commits without force-pushing? In Subversion you can just do svn propedit svn:log --revlog -r, but for git? I have edited my own log message recently to improve it and I know that others do it to indicate that a commit was reverted by a future revision or to add CVE numbers after vulnerabilities are public. Would we loose this possibility with git? Regards Rüdiger
