Patch preparation for GSoC evaluation

[Denis Obrezkov]

2017-08-11 11:53 GMT+02:00 Sebastian Huber <
sebastian.huber at embedded-brains.de>:

> On 11/08/17 11:44, Denis Obrezkov wrote:
>
> during our last meeting I didn't completely understand what to do
>> with my commits.
>>
>> I have a set of commits made during the GSoC, they are, of course,
>> a bit chaotic. And the only last few commits make my code look better.
>> So, I have a question: should I take all my commits,
>> merge them into one big commit which changes the state of the code
>> from the initial to the current state? Or how should I clean my commit
>> history?
>>
>
> Ideally, there should be a patch set, that can be integrated into RTEMS
> with clean, self-contained, well described and easy to review patches.
>
> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone   : +49 89 189 47 41-16
> Fax     : +49 89 189 47 41-09
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
>
Would it be appropriate to provide a set of patches, for example,
for uart, clock and linkcmd related code, but without saving a commit
history?
I mean - to make a git reset --mixed and then make new commits with
relatively
clean code.

-- 
Regards, Denis Obrezkov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20170811/2a9e4d46/attachment-0002.html>