James Nylen jny...@gmail.com writes:
I don't agree that removing `--annotate` obviates the need for `--unannotate`.
I responded on 1/17 with what I think is a typical and normal use case
for that option:
Sorry, I must have missed that reply.
- add fancylib as a subtree of myprog
-
On Mon, Feb 18, 2013 at 1:39 PM, gree...@obbligato.org wrote:
James Nylen jny...@gmail.com writes:
- add fancylib as a subtree of myprog
- commit to myprog repo: fancylib: don't crash as much
- split these commits back out to fancylib main repo, and remove
the fancylib: prefix
Should
From: David A. Greene gree...@obbligato.org
Remove --annotate. This obviates the need for an --unannotate
command. We really want a more generalized commit message rewrite
mechanism.
Signed-off-by: David A. Greene gree...@obbligato.org
---
contrib/subtree/git-subtree.sh |6 +
On Tue, Feb 5, 2013 at 6:44 AM, gree...@obbligato.org wrote:
Junio C Hamano gits...@pobox.com writes:
Remove --annotate. This obviates the need for an --unannotate
command. We really want a more generalized commit message rewrite
mechanism.
That may be a good goal as the end result, but
From: David A. Greene gree...@obbligato.org
Remove --annotate. This obviates the need for an --unannotate
command. We really want a more generalized commit message rewrite
mechanism.
Signed-off-by: David A. Greene gree...@obbligato.org
---
contrib/subtree/git-subtree.sh |6 +
David A. Greene gree...@obbligato.org writes:
From: David A. Greene gree...@obbligato.org
Remove --annotate. This obviates the need for an --unannotate
command. We really want a more generalized commit message rewrite
mechanism.
That may be a good goal as the end result, but wouldn't it
6 matches
Mail list logo
