Re: [bug] Working files created in bare repository when pushing to a rewound bare repository

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 3, 2008, 21:29 UTC
Message-ID: <7v3atepph1.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <20071231072632.GA11451@coredump.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 15 quoted lines

> And then on top of this (plus one-liner fix I posted), as Ping Yin
> suggested, we can do:
>
> -- >8 --
> git-reset: default to --soft in a bare repo
>
> --mixed doesn't make sense, since we don't generally have an
> index.
>
> Signed-off-by: Jeff King <peff@peff.net>
> ---
> This is a bit more contentious. There's no reason you can't have an
> index in a bare repo, and this is changing the behavior of those who do.
> They can always explicitly specify --mixed (since we haven't disallowed
> that), but it might break some scripts.

I'd prefer to error out if something does not make sense rather than defaulting differently depending on the bareness of the repository, but that is probably the matter of taste.

Please re-raise the issue post 1.5.4