git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Lars Hjemli <hjemli@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [RFC/PATCH 0/3] Enable in-process submodule traversal
Date: Mon, 12 Jan 2009 00:45:52 +0100	[thread overview]
Message-ID: <1231717555-10559-1-git-send-email-hjemli@gmail.com> (raw)

This patch series implements basic support for traversing the tree objects
in submodules when the linked commit object is reachable. Normally such
linked commit objects will not be reachable in the containing repository,
but adding local copies of submodule repositories as alternate object
databases for the containing repo solves this issue.

The first patch in the series does all the 'hard work' required for the
traversal to work, while the next two patches adds a '--submodules' flag
to git-archive and git-ls-tree as proof of concept.

Lars Hjemli (3):
  tree.c: add support for traversal of submodules
  archive.c: enable traversal of submodules
  builtin-ls-tree: enable traversal of submodules

 archive.c         |    2 ++
 builtin-ls-tree.c |   23 ++++++++---------------
 tree.c            |   20 +++++++++++++++++---
 tree.h            |    1 +
 4 files changed, 28 insertions(+), 18 deletions(-)

             reply	other threads:[~2009-01-12  0:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-11 23:45 Lars Hjemli [this message]
2009-01-11 23:45 ` [RFC/PATCH 1/3] tree.c: add support for traversal of submodules Lars Hjemli
2009-01-11 23:45   ` [RFC/PATCH 2/3] archive.c: enable " Lars Hjemli
2009-01-11 23:45     ` [RFC/PATCH 3/3] builtin-ls-tree: " Lars Hjemli
2009-01-12  3:15   ` [RFC/PATCH 1/3] tree.c: add support for " Junio C Hamano
2009-01-12  9:04     ` Lars Hjemli
2009-01-12 10:07       ` Junio C Hamano
2009-01-12 10:59         ` Lars Hjemli
2009-01-12  2:07 ` [RFC/PATCH 0/3] Enable in-process submodule traversal 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1231717555-10559-1-git-send-email-hjemli@gmail.com \
    --to=hjemli@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).