[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] SMP initialization: detection and enumeration OFF TOPIC PRAI

From: Amos Jeffries
Subject: Re: [PATCH] SMP initialization: detection and enumeration OFF TOPIC PRAISE
Date: Wed, 12 Aug 2020 00:19:01 +1200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0

On 11/08/20 11:57 pm, Samuel Thibault wrote:
> Almudena Garcia, le mar. 11 août 2020 13:45:19 +0200, a ecrit:
>>> P.S.  You might be interested in using the program git send-email.
>>> Apparently it makes it really easy to send in a patches series.  It's
>>> actually what GNU Guix contributing guidelines recommends.
>> My problem is that, in my internal repository, I do many commits for each
>> change (even for each file). The development is progressive.
>> Then, if I take the commit history to generate my patches, I would generate
>> many spurious patches, making it very difficult to check and apply them.
> Sure, that's a common thing when developping.
>> Even doing a rebase over another branch, the rebase adds the commit history, 
>> so
>> I keep the same problem.
> ? On the contrary, rebase lets you decide what exactly you keep in the
> history and what you squash.


To clarify in case you are not aware. The "rebase -i" operation is what
is being suggested. The -i option enables much more flexibility of
control over the patch sequence and history during rebase.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]