Re: [RFC - draft] List of proposed future changes that are backward incompatible

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

Re: [RFC - draft] List of proposed future changes that are backward incompatible

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

Björn Steinbrink [off-list ref] writes:
How about having the default in the code being a warning, but the
default for new repos being "reject"?
To reserve time to manage git itself, I will try not to point people to
previous discussions, but I'd like help from people who've already seen
the previous discussions to do so.  This is one of the things that was
proposed and already shot down.

Re: [RFC - draft] List of proposed future changes that are backward incompatible

From: Björn Steinbrink <hidden>
Date: 2016-06-15 22:46:12

On 2009.02.16 00:49:52 -0800, Junio C Hamano wrote:
Björn Steinbrink [off-list ref] writes:
quoted
How about having the default in the code being a warning, but the
default for new repos being "reject"?
To reserve time to manage git itself, I will try not to point people to
previous discussions, but I'd like help from people who've already seen
the previous discussions to do so.  This is one of the things that was
proposed and already shot down.
OK, I'm sorry. Seems that my quick look through the other thread was too
quick :-(

Björn
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help