public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Martin Waitz <tali@admingilde•org>
To: git@vger•kernel.org
Subject: RFC: submodule terminology
Date: Sun, 20 May 2007 23:44:17 +0200	[thread overview]
Message-ID: <20070520214417.GM5412@admingilde.org> (raw)

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

hoi :)

I think we should agree to one name for what currently is named
submodule / subproject / dirlink / gitlink.

Or use one name for the low-level plumbing (have a tree entry
which points to another commit): dirlink or gitlink and another
one for the high-level UI think: submodule or subproject.
But then we should use those names consequently.

Oppinions?

-- 
Martin Waitz

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

             reply	other threads:[~2007-05-20 21:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-20 21:44 Martin Waitz [this message]
2007-05-20 22:06 ` RFC: submodule terminology Johan Herland
2007-05-20 22:59   ` Junio C Hamano
2007-05-20 23:10     ` Johan Herland
2007-05-21  6:44     ` Raimund Bauer
2007-05-21  6:52       ` Shawn O. Pearce
2007-05-20 23:03   ` Martin Waitz
2007-05-20 23:16     ` Johan Herland
2007-05-20 23:39       ` Martin Waitz
2007-05-21  0:32         ` Eric Lesh

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=20070520214417.GM5412@admingilde.org \
    --to=tali@admingilde$(echo .)org \
    --cc=git@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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