Re: Understanding version 4 packs

From: Shawn O. Pearce <spearce@spearce.org>
Date: Mar 27, 2007, 06:55 UTC
Message-ID: <20070327065531.GN13247@spearce.org>
In-Reply-To: <e5bfff550703262346q54853791scca3bab217a043aa@mail.gmail.com>

Marco Costalba <mcostalba@gmail.com> wrote:

Show 18 quoted lines

> On 3/26/07, Nicolas Pitre <nico@cam.org> wrote:
> >Hence, the path component table would contain:
> >
> >        drivers
> >        usb
> >        host
> >        Kconfig
> >        Makefile
> >        ehci.h
> >        ehci-pci.c
> >        ohci-pci.c
> >        sched.c
> >
> >along with the mode bits for each of those path components, and this is
> >what the new tree object would index into for each tree record.
> 
> Just a question. So getting full paths does it requires some additional 
> work?

No.

Why? Because Git already makes the full path by taking individual path components from each tree object and joins them together (adding a "/" between each component) before displaying it to an application, or loading the path into the index file. This is because of the fundemental (and quite nice!) structure of a tree.

-- 
Shawn.