example of a nanny state IMO, trying to dictate what git commands to use, or what editor to use. Maybe this works for you in your corporate hellholes, but I think some folks have a bit of a power issue, are accustomed to dictacting this stuff to their employees and so on, but this is open-source. I don't report to you, i dont use the editor you tell me, or the git commands you tell me.
On Sat, Nov 4, 2023 at 8:21 AM Uwe Schindler <u...@thetaphi.de> wrote: > > Hi, > > I just wanted to give your attention to the following discussion: > https://github.com/apache/lucene/pull/12737#issuecomment-1793426911 > > From my knowledge the Lucene (and Solr) community decided a while back > to disable merging and only allow squashig of PRs. Robert always did > this, but because of a one-time problem with two branches he was working > on in parallel, he suddenly changed his mind and did merges on his own, > not sqashing the branch and pushing to ASF Git. > > I am also not a fan of removing all history, but especially for heavy > committing branches like the given PR, I think we should invite our > committers to also adhere to community standards everyone else > practices. I would agree with merging those branches if all commit > messages in the branch would be well-formed with issue ID or PR number, > but in the above case you get a history of random commits which is no > longer linear and not easy readable. > > What do others think? > > Uwe > > -- > Uwe Schindler > Achterdiek 19, D-28357 Bremen > https://www.thetaphi.de > eMail: u...@thetaphi.de > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
