Re: [RFC - draft] List of proposed future changes that are backward incompatible
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Feb 16, 2009, 10:23 UTC
- Message-ID
- <alpine.DEB.1.00.0902161121290.10279@pacific.mpi-cbg.de>
- In-Reply-To
- <alpine.DEB.1.10.0902151636510.14911@asgard.lang.hm>
Hi,
On Sun, 15 Feb 2009, david@lang.hm wrote:
> please be careful with the term 'deprecated', just becouse you would do > something a different way doesn't make it 'deprecated', that term should > only be used for features that are on their way out of the product, but > haven't been removed yet.
It is not deprecated because I do not like it. Actually, I am pretty indifferent about the pushing into a non-bare repository.
It is deprecated because a lot of people active in the Git community spend a real lot of time explaining to a whole bunch of new users on IRC and recently even on this list why their pushing into a non-bare repository does not work, and why their suggestions how to solve the issue does not work either.
Hth, Dscho