> years of preaching "don't rebase unnecessarily" and "don't create
> spurious dependencies" being mostly ineffective. 

I speak for all the people who play "Myst" by just walking around the island 
enjoying the views and listening to the waves.

We don't know when it is necessary to rebase, except when we get the message 
"Please rebase the change locally...," and even then we don't really understand 
what is wrong. And we don't know when we are creating spurious dependencies 
because we don't know we are creating dependencies at all.  We just do:

git commit -a -F ./commit.txt
git pull --rebase
git push origin HEAD:refs/for/dev

We do the rebase step because we were told that was the right thing. In Myst, 
how do you get out to that island to pull the lever?

 martin
________________________________________
From: [email protected] 
<[email protected]> on behalf of 
Joerg Bornemann <[email protected]>
Sent: Friday, October 24, 2014 11:45 AM
To: [email protected]
Subject: Re: [Development] [FYI] new git-gpush features, a.k.a. the smart way 
of pushing to gerrit

On 24-Oct-14 11:37, Oswald Buddenhagen wrote:

>> What is rationale for the "technical enforcement"?
>>
> years of preaching "don't rebase unnecessarily" and "don't create
> spurious dependencies" being mostly ineffective. "i pushed an update to
> your change, take care not to overwrite it accidentally" being futile on
> a regular basis. people demanding ridiculously short review cycles,
> because waiting for a review "holds them up for 'process' reasons". etc.
> iow, the usual results of inattentivenes, indifference (unless one is
> the reviewer affected by it, of course), impatience, and sheer laziness.
> and sometimes even genuine mistakes.

I for one already did this manually where it made sense.
Some of us don't.

Anyways, you missed the chance to convince people from the awesomeness
of your script before pissing everybody off with your megalomania.


Joerg
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________
Development mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/development

Reply via email to