Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:Double ACK. I'm in complete agreement with every point Dscho has made in this thread, even if I haven't quoted it. ;-) I *really* do not want to see "<tree-ish>:<path>" to mean include the current prefix, *especially* when a bare repository is involved. I often either do ad-hoc git-show lines against bare repositories, or have scripts that depend on this existing absolute path behavior. I'd like to see those not break. ;-) Since "." and ".." should not be valid names in any tree of a Git repository I think we're OK to say that ":./" and ":../" are to imply relative to current prefix. But if we do ":../" then we also have to do ":../../../../../../.." ;-) -- Shawn. - 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 006/196] Chinese: add translation of oops-tracing.txt |
| Andrew Morton | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Eric W. Biederman | [PATCH] nfs lockd reclaimer: Convert to kthread API |
| James Bottomley | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
