git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Martin Waitz <tali@admingilde.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>,
	git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: Re: Subprojects tasks
Date: Sun, 17 Dec 2006 20:54:17 +0100	[thread overview]
Message-ID: <20061217195417.GI12411@admingilde.org> (raw)
In-Reply-To: <200612171529.03165.jnareb@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

hoi :)

On Sun, Dec 17, 2006 at 03:29:02PM +0100, Jakub Narebski wrote:
> By the way, should this ref be in submodule, or in supermodule, e.g. in
> refs/modules/<name>/HEAD? And there is a problam _what_ branch should
> be that.

At the moment I simply use refs/heads/master of the submodule
repository, just because it is the default branch anyway.

In order to make the submodule refs which are not added to the
supermodule available to the supermodule anyway (for fsck and prune),
I added a symlink .git/refs/module/<submodule> -> <submodule>/.git/refs,
so that the submodule branch is also available as
refs/module/<submodule>/heads/master in the supermodule.

But I expect that all this setup stuff can be greatly simplified with a
little bit more knowledge of submodules in the core.  But this cleanup
is for later, when the basis is settled.

-- 
Martin Waitz

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-12-17 19:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-16 18:32 Subprojects tasks Junio C Hamano
2006-12-16 18:45 ` Jakub Narebski
2006-12-16 23:01   ` Martin Waitz
2006-12-16 23:15     ` Jakub Narebski
2006-12-17  0:01       ` Josef Weidendorfer
2006-12-17 11:45         ` Martin Waitz
2006-12-17 13:01           ` Jakub Narebski
2006-12-17 13:48             ` Martin Waitz
2006-12-17 14:29               ` Jakub Narebski
2006-12-17 19:54                 ` Martin Waitz [this message]
2006-12-17 23:27                   ` Josef Weidendorfer
2006-12-18  7:45                     ` Martin Waitz
2006-12-17 23:23               ` Josef Weidendorfer
2006-12-18  7:44                 ` Martin Waitz
2006-12-18 10:30                   ` Josef Weidendorfer
2006-12-17  0:08       ` Josef Weidendorfer
2006-12-16 20:35 ` Sven Verdoolaege
2006-12-16 21:07   ` Junio C Hamano
2006-12-16 22:58     ` Martin Waitz
2006-12-16 23:14       ` Sven Verdoolaege
2006-12-17  0:32       ` Josef Weidendorfer
2006-12-17  8:48 ` Alan Chandler
2006-12-17 10:01   ` Jakub Narebski
2006-12-17 11:17 ` Martin Waitz

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=20061217195417.GI12411@admingilde.org \
    --to=tali@admingilde.org \
    --cc=Josef.Weidendorfer@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=junkio@cox.net \
    /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).