Re: [PATCH] contrib/subtree: Remove --annotate

2016-06-28 Thread David A. Greene
Junio C Hamano writes: > gree...@obbligato.org (David A. Greene) writes: > >> Just to clarify, what is the expectation of things in contrib? >> Basically the same as other code? > > That heavily depends on your exit strategy. > > If the aspiration is to move up to exit, then the quality and > sta

Re: [PATCH] contrib/subtree: Remove --annotate

2016-01-05 Thread David A. Greene
Junio C Hamano writes: > David Greene writes: > >> From: "David A. Greene" >> >> Remove --annotate. This obviates the need for an --unannotate >> command, which is both an obvious addition and difficult to define >> due to the numerous ways one might want to specify how to edit >> commit messa

Re: [PATCH] contrib/subtree: Remove --annotate

2016-01-05 Thread Junio C Hamano
David Greene writes: > From: "David A. Greene" > > Remove --annotate. This obviates the need for an --unannotate > command, which is both an obvious addition and difficult to define > due to the numerous ways one might want to specify how to edit > commit messages. git has other tools more sui

[PATCH] contrib/subtree: Remove --annotate

2016-01-04 Thread David Greene
From: "David A. Greene" Remove --annotate. This obviates the need for an --unannotate command, which is both an obvious addition and difficult to define due to the numerous ways one might want to specify how to edit commit messages. git has other tools more suited to rewriting commit messages a

Re: [PATCH] contrib/subtree: Remove --annotate

2016-01-04 Thread greened
Sebastian Schuberth writes: > On Sat, Jan 2, 2016 at 9:36 PM, David Greene wrote: > >> commit messages. git has other tools more suited to rewriting >> commit messages and it's easy enough to use them after a subtree >> split. > > For completeness, it probably would be a good idea to name examp

Re: [PATCH] contrib/subtree: Remove --annotate

2016-01-03 Thread Sebastian Schuberth
On Sat, Jan 2, 2016 at 9:36 PM, David Greene wrote: > commit messages. git has other tools more suited to rewriting > commit messages and it's easy enough to use them after a subtree > split. For completeness, it probably would be a good idea to name examples for such more suitable tools as par

[PATCH] contrib/subtree: Remove --annotate

2016-01-02 Thread David Greene
From: "David A. Greene" Remove --annotate. This obviates the need for an --unannotate command, which is both an obvious addition and difficult to define due to the numerous ways one might want to specify how to edit commit messages. git has other tools more suited to rewriting commit messages a