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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 21/12/2012 18:01, Junio C Hamano ha scritto:
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
Manlio Perillo manlio.peri...@gmail.com writes:
I lose the history of all the changes I have made to produce the final
version of a patch.
Since for every new version of a patch I do a commit --amend, I can not
see, as an example, the changes I have made between x and y versions of
a patch.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il 21/12/2012 19:17, Junio C Hamano ha scritto:
[...]
Of course you can plan ahead (this is what I usually do when working
on a series that is not how about this throw-away patch I send to
this list all the time) and name the topic topic-v1, fork
On Fri, Dec 21, 2012 at 1:30 PM, Manlio Perillo
manlio.peri...@gmail.com wrote:
By the way, I would also like to be able to set the default value for
the --output option in config file; something like:
[format]
output = +mp/$(git symbolic-ref --short HEAD)
where the string will be
5 matches
Mail list logo
