Re: [PATCH] Implement git commit as a builtin command.

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH] Implement git commit as a builtin command.

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:46

Karl Hasselström [off-list ref] writes:
On 2007-11-01 21:14:45 +0100, Jakub Narebski wrote:
quoted
Kristian H?gsberg wrote:
quoted
Move git-commit.sh to contrib/examples.
Just a note: you might want to use "git format-patch -M".
I wonder if it would be such a bad idea to make this the default. It
seems like _everyone_ who should be using it forget it. And the number
of patches made for human or git consumption is probably vastly larger
than the number of patches made for consumption by other tools.
On this mailing list, we can pretty much assume that renaming
diff can be applied by people.  But outside world is a different
story.

Re: [PATCH] Implement git commit as a builtin command.

From: Karl Hasselström <hidden>
Date: 2016-06-15 22:43:46

On 2007-11-02 02:37:43 -0700, Junio C Hamano wrote:
Karl Hasselström [off-list ref] writes:
quoted
I wonder if it would be such a bad idea to make this the default.
It seems like _everyone_ who should be using it forget it. And the
number of patches made for human or git consumption is probably
vastly larger than the number of patches made for consumption by
other tools.
On this mailing list, we can pretty much assume that renaming diff
can be applied by people. But outside world is a different story.
So I guess a prerequisite for this is to get git patch format support
into GNU patch, then? :-)

-- 
Karl Hasselström, kha@treskal.com
      www.treskal.com/kalle
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help