From: Junio C Hamano <gitster@pobox.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Thomas Rast <trast@student.ethz.ch>,
Git Mailing List <git@vger.kernel.org>,
in-gitvger@baka.org
Subject: Re: Submodules or similar for exercise/exam management
Date: Thu, 18 Nov 2010 14:32:53 -0800 [thread overview]
Message-ID: <7vsjyyb6ui.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <4CE5988F.7050309@web.de> (Jens Lehmann's message of "Thu\, 18 Nov 2010 22\:20\:15 +0100")
Jens Lehmann <Jens.Lehmann@web.de> writes:
>> 3) never need to be aware of repo boundaries or manipulate sub-repo
>
> I think that this requirement is the hardest for any solution I know
> of or can imagine, as you hit these boundaries sooner or later either
> when you want to commit, push and/or when you have to resolve merge
> conflicts.
Just a quick sanity check. When this "requirement" makes sense, does the
whole thing need to be a superproject with bunch of submodules, and why?
next prev parent reply other threads:[~2010-11-18 22:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-18 10:09 Submodules or similar for exercise/exam management Thomas Rast
2010-11-18 16:36 ` Seth Robertson
2010-11-22 13:20 ` Thomas Rast
2010-11-18 21:20 ` Jens Lehmann
2010-11-18 22:32 ` Junio C Hamano [this message]
2010-11-18 23:49 ` Jonathan Nieder
2010-11-22 13:56 ` Thomas Rast
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=7vsjyyb6ui.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=in-gitvger@baka.org \
--cc=trast@student.ethz.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.