From: Junio C Hamano <junkio@cox.net>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org, Petr Baudis <pasky@ucw.cz>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [RFC] Support projects including other projects
Date: Wed, 11 May 2005 22:37:10 -0700 [thread overview]
Message-ID: <7v8y2lknsp.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0505120057250.30848-100000@iabervon.org> (Daniel Barkalow's message of "Thu, 12 May 2005 01:19:13 -0400 (EDT)")
>>>>> "DB" == Daniel Barkalow <barkalow@iabervon.org> writes:
DB> When a particular cogito commit is made, it is impossible to tell whether
DB> the next git-pb will work with it; the current set of patches could be
DB> rejected in mainline git, and different support for the same functionality
DB> added which requires something different from cogito...
... Many problems with the approach of saying "this Cogito
requires this git-pb" omitted here; I agree that alone
may not solve problems ...
DB> I think your idea is theoretically possible, but that it is just too
DB> impractical...
I do not think it is my idea. Maybe I misunderstood what you
meant, but here is what you wrote in the message I responded to.
... There is a bit of convenience to having the tools magically
do the right thing when you check out the child project, but the
thing that really requires tool support is that you need to be
able to find the version of git-pb which matches the version of
cogito you're trying to build (and you might be searching the
history for where a bug was introduced, so you may not be able
to use the latest of either).
That part is fine. I already agreed that recording such version
dependency would be a good thing. I disagreed with the
"solution", however, of having that recorded at the core level:
The solution is to add a header to commits: "include {hash}",
which simply says that the given hash, which is from the core
project, is the commit needed to build this commit of the
non-core project. This comes from an argument to commit-tree
("-I", perhaps), and the parsing code needs to identify the
reference so that fsck-cache stays happy.
I do not think the issues you are raising are solved by having
that "include {hash}" thing in the commit like you propose here,
instead of keeping it outside of the commit like I suggested.
What I meant to say was just I do not think having this "version
dependency" in the core or outside of the core would make any
difference.
next prev parent reply other threads:[~2005-05-12 5:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 4:23 [RFC] Support projects including other projects Daniel Barkalow
2005-05-12 4:52 ` Junio C Hamano
2005-05-12 5:19 ` Daniel Barkalow
2005-05-12 5:37 ` Junio C Hamano [this message]
2005-05-12 6:04 ` Daniel Barkalow
2005-05-12 6:28 ` Junio C Hamano
2005-05-12 16:51 ` Daniel Barkalow
2005-05-12 17:24 ` David Lang
2005-05-12 18:47 ` Junio C Hamano
2005-05-12 19:12 ` Daniel Barkalow
2005-05-12 6:14 ` Junio C Hamano
2005-05-12 5:37 ` James Purser
2005-05-12 5:46 ` Daniel Barkalow
2005-05-12 6:33 ` James Purser
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=7v8y2lknsp.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=pasky@ucw.cz \
--cc=torvalds@osdl.org \
/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).