Re: recommendation for patch maintenance

2012-12-21 Thread Junio C Hamano
On Fri, Dec 21, 2012 at 1:30 PM, Manlio Perillo 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 processed by the shel

Re: recommendation for patch maintenance

2012-12-21 Thread Manlio Perillo
-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"

Re: recommendation for patch maintenance

2012-12-21 Thread Junio C Hamano
Manlio Perillo 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. > > Of course the

Re: recommendation for patch maintenance

2012-12-21 Thread Manlio Perillo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Il 21/12/2012 18:01, Junio C Hamano ha scritto: > Manlio Perillo 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 revi

Re: recommendation for patch maintenance

2012-12-21 Thread Junio C Hamano
Manlio Perillo 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: > >

recommendation for patch maintenance

2012-12-21 Thread Manlio Perillo
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. 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