On 6 September 2016 at 15:21, Marc Dequènes (Duck) <duck@redhat.com> wrote:
On 09/06/2016 09:15 PM, Marc Dequènes (Duck) wrote:
That is not very practical in this case. I'd like to preserve the work history, as said in the meeting.
I mean in most cases squashing is perfectly fine, unless it is very big, so I agree with this method. I'm just looking for a way to get the previous work history, so this is a one-shot situation.
As the previous way of pushing changes was different, there is no other way to also push the logic motivating the changes. After, reviews would take over.
I find that typically work history can be lease then ideal for presenting work to other developers. For me I typically find that I can narrow down commits by a factor of 3-5 when going from actual work history to a commit series that describes gradual accumulation of major features. Please not that I did not mean that you should squash all commits to a single big one, just narrow them down and reorder to make it easier for us to understand your major themes and ideas. -- Barak Korren bkorren@redhat.com RHEV-CI Team