Re: a few remaining issues...
- From
Junio C Hamano <junkio@cox.net>
- Date
- Jan 8, 2007, 21:59 UTC
- Message-ID
- <7vr6u5uqm6.fsf@assigned-by-dhcp.cox.net>
- In-Reply-To
- <7v7iw1hgvt.fsf@assigned-by-dhcp.cox.net>
Updates to the previous "remaining issues" list before 1.5.0.
* Bare repository.
I think what I have in 'next' to add 'core.bare' configuration to make the bare repository detection safer is ready to be used to port the RFC patch from Shawn to forbid working-tree operations in a bare repository to prevent accidents from happening. It would be nice if we can cook it for a few days in 'next' and push it out to 'master' before v1.5.0-rc1.
Volunteers?
* Packed refs.
'git-pack-refs' should default to --prune. There is no point not to, really. Objections?
We _might_ want to teach 'git-pack-refs' how to unpack, although there is no real need for it. I do not care too deeply either way.
* Detached HEAD.
This is now in 'master' ;-).
* Make -u default to 'git-am'.
Since we are talking about allowing potentially incompatible UI changes in v1.5.0 iff the change improves the general situation, I would say why not. I'd add --no-utf8 just in case, but personally I do not offhand see need for it. Projects that want their commit log messages in legacy encoding can and should say "i18n.commitencoding = EUCJP" or somesuch and they can continue using their preferred encodings without changing their tools nor work habit and without having to worry about re-coding errors.