From: Thomas Gummerer <t.gummerer@gmail.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: git@vger.kernel.org, trast@student.ethz.ch, gitster@pobox.com,
mhagger@alum.mit.edu
Subject: Re: [GSoC] Designing a faster index format - Progress report
Date: Fri, 25 May 2012 22:15:47 +0200 [thread overview]
Message-ID: <20120525201547.GB86874@tgummerer> (raw)
In-Reply-To: <CACsJy8As2SQwEi2vHAQA+OeH+TjoCzzcknFbQ2tGXaWX7zsHVA@mail.gmail.com>
On 05/25, Nguyen Thai Ngoc Duy wrote:
> On Wed, May 23, 2012 at 7:21 PM, Thomas Gummerer <t.gummerer@gmail.com> wrote:
> > == Outlook for the next week ==
> >
> > - Start working on actual git code
> > - Read the header of the new format
>
> I know it's out of scope, but it would be great if you could make
> ls-files read the new index format directly. Having something that
> actual works will ensure we don't overlook anything in the new format.
> We can then learn from ls-files lesson (especially how to handle both
> new/old format) and come up with api/in-core structures for the rest
> of git later.
Thanks for your suggestion. How did you think this should be done?
Writing a extra function in ls-files, just for outputting? I don't
think it is necessary to write a extra function, since the result
from the read_index_from function in read-cache is used for that
anyway. Or did you have something different in mind, that I'm missing
here?
--
Thomas
next prev parent reply other threads:[~2012-05-25 20:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 12:21 [GSoC] Designing a faster index format - Progress report Thomas Gummerer
2012-05-24 20:01 ` Thomas Rast
2012-05-24 20:57 ` Junio C Hamano
2012-05-25 11:31 ` Nguyen Thai Ngoc Duy
2012-05-25 20:15 ` Thomas Gummerer [this message]
2012-05-26 4:09 ` Nguyen Thai Ngoc Duy
2012-05-27 9:04 ` Thomas Gummerer
2012-05-27 9:27 ` Junio C Hamano
2012-05-27 12:23 ` Nguyen Thai Ngoc Duy
2012-05-28 8:26 ` Thomas Gummerer
2012-05-29 13:29 ` Thomas Rast
2012-05-29 13:43 ` Nguyen Thai Ngoc Duy
2012-05-29 18:33 ` Junio C Hamano
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=20120525201547.GB86874@tgummerer \
--to=t.gummerer@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mhagger@alum.mit.edu \
--cc=pclouds@gmail.com \
--cc=trast@student.ethz.ch \
/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).