From: "Shawn O. Pearce" <spearce@spearce.org>
To: Marco Costalba <mcostalba@gmail.com>
Cc: Nicolas Pitre <nico@cam.org>,
Peter Eriksen <s022018@student.dtu.dk>,
git@vger.kernel.org
Subject: Re: Understanding version 4 packs
Date: Tue, 27 Mar 2007 02:55:31 -0400 [thread overview]
Message-ID: <20070327065531.GN13247@spearce.org> (raw)
In-Reply-To: <e5bfff550703262346q54853791scca3bab217a043aa@mail.gmail.com>
Marco Costalba <mcostalba@gmail.com> wrote:
> 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.
next prev parent reply other threads:[~2007-03-27 6:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-24 20:23 Understanding version 4 packs Peter Eriksen
2007-03-24 23:24 ` Nicolas Pitre
2007-03-25 8:35 ` Peter Eriksen
2007-03-25 9:18 ` Shawn O. Pearce
2007-03-25 17:09 ` Linus Torvalds
2007-03-25 20:31 ` Shawn O. Pearce
2007-03-26 1:12 ` Nicolas Pitre
2007-03-26 2:02 ` Shawn O. Pearce
2007-03-26 8:49 ` Jakub Narebski
2007-03-26 14:01 ` Nicolas Pitre
2007-03-26 12:16 ` Marco Costalba
2007-03-26 14:27 ` Nicolas Pitre
2007-03-26 17:10 ` Marco Costalba
2007-03-26 18:15 ` Nicolas Pitre
2007-03-26 18:43 ` Nicolas Pitre
2007-03-27 6:46 ` Marco Costalba
2007-03-27 6:55 ` Shawn O. Pearce [this message]
2007-03-25 8:46 ` Shawn O. Pearce
2007-03-25 9:40 ` Shawn O. Pearce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070327065531.GN13247@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=mcostalba@gmail.com \
--cc=nico@cam.org \
--cc=s022018@student.dtu.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).