Manlio Perillo <manlio.peri...@gmail.com> writes:

> I would like to have advices about some possible workflows to use when
> maintaining a patch, that can evolve over the time (fixing bugs, and
> applying advices from reviewers).
>
> In my case I have a single commit to maintain.
>
>
> The workflow I use now is this:
>
>   1) create a topic branch, e.g. mp/complete-path
>   2) write code
>   3) commit
>   4) format-patch --output=mp/complete-patch master
>   5) review the patch
>   6) send-email
>
> when I need to update the patch:
>
>   1) modify code
>   2) commit --amend
>   3) format-patch --subject-prefix="PATCH v<n>" \
>      --output=mp/complete-patch master
>   4) edit patch to add a list of what was changed
>   5) review the patch
>   6) send-email
>
> This is far from ideal, since all my local changes are lost.

Not offering any answer, but it is unclear to me what local changes
you are losing here.  Care to explain?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to