Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: git@vger.kernel.org, Daniel Barkalow <barkalow@iabervon.org>,
	Petr Baudis <pasky@suse.cz>
Subject: Re: Notes on Subproject Support
Date: Sat, 28 Jan 2006 13:43:30 -0800	[thread overview]
Message-ID: <7vfyn8t4e5.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200601280455.k0S4tx6N003251@laptop11.inf.utfsm.cl> (Horst von Brand's message of "Sat, 28 Jan 2006 01:55:59 -0300")

Horst von Brand <vonbrand@inf.utfsm.cl> writes:

> One thing that has bugged me from the beginning of this, and which does
> come out of your example: Why only project/subproject? In your example, you
> have the kernel (OK(ish)) and "rest of the world",...

Because I presented the example badly, perhaps?

There is nothing that prevents you from having more "bind" lines
than the example showed, to have one project that works with N
subprojects.  In fact, the examples in earlier threads used a
project with the kernel and gcc subprojects -- I just felt it
was so obvious you can do N subprojects instead of just one, so
used just one subproject in the latest round of example for the
sake of brevity.

And there is nothing that prevents you from having "bind" lines
in the subproject commit objects, either.

The structure the lower level objects support with the "bound
commit" extension is not about "project vs subproject".  You can
express "project that has subprojects each of which has
subsubprojects".

Now, it is totally a separate issue that anybody sane would want
to keep track of such structure, or we would be better off
leaving it to build infrastructure specific to each toplevel
project, as argued by some earlier.

      reply	other threads:[~2006-01-28 21:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23  1:35 Notes on Subproject Support Junio C Hamano
2006-01-23  3:50 ` Daniel Barkalow
2006-01-23  4:36   ` Junio C Hamano
2006-01-23  5:48     ` Junio C Hamano
2006-01-23  6:06       ` Alexander Litvinov
2006-01-23 16:48         ` Daniel Barkalow
2006-01-23  8:38       ` Junio C Hamano
2006-01-23 17:57       ` Daniel Barkalow
2006-01-24  1:50         ` Junio C Hamano
2006-01-23 16:31     ` Daniel Barkalow
2006-01-24  1:50       ` Junio C Hamano
2006-01-24  4:22         ` Daniel Barkalow
2006-01-23  8:00 ` Junio C Hamano
2006-01-23 12:50 ` Martin Atukunda
2006-01-23 19:30   ` Junio C Hamano
2006-01-28  4:55 ` Horst von Brand
2006-01-28 21:43   ` Junio C Hamano [this message]

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=7vfyn8t4e5.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    --cc=vonbrand@inf.utfsm.cl \
    /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