On Thu, Aug 28, 2008 at 2:54 PM, Al Viro wrote:
Sorry, I guess I should have made it clearer.
I haven't made my mind about git-foo vs "git foo", but a decision has
been made to deprecate git-foo, and allow it as an option for the
people that really want to use it, right?
So there must have been a reason to deprecate git-foo, if people keep
using git-foo, and distributions keep allowing it, what's the point of
deprecation? It's ok if they keep that usage to themselves, like
'alias ll = ls -l', but it's not something to assume everybody uses.
So either we take back the decision and keep discussing if it's a good
idea to deprecate git-foo, or we go forward and discourage git-foo
completely.
Anything in the middle would just confuse people more, and wouldn't
achieve the purpose of deprecation.
If some script is relying on git-foo, and it has been deprecated, it
should be fixed.
Best regards.
--
Felipe Contreras
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| David Chinner | Re: [RFD] BIO_RW_BARRIER - what it means for devices, filesystems, and dm/md. |
| Andrew Morton | -mm merge plans for 2.6.23 |
| Trent Piepho | Re: [PATCH] [POWERPC] Improve (in|out)_beXX() asm code |
git: | |
| David Miller | Re: iptables very slow after commit784544739a25c30637397ace5489eeb6e15d7d49 |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
