From: username localhost <username.localhost@gmail.com>
To: git@vger.kernel.org
Subject: Re: organizing multiple repositories with dependencies
Date: Sat, 28 Apr 2012 17:31:54 +0000 (UTC) [thread overview]
Message-ID: <loom.20120428T191337-86@post.gmane.org> (raw)
In-Reply-To: nngobqg1ztl.fsf@transit.us.cray.com
dag writes:
>
> Should gitslave be covered in this document if gitslave is not in the
> upstream git repository? I'm not knocking gitslave, in fact I think
> it's cool technology and probably _should_ be contributed upstream. I'm
> just asking the question about whether stuff in Documentation/ is or
> should be limited to things in the upstream repository.
I think that it would be better to be inclusive while initially writing such a
document. The work of helping to distinguish gitslave from the others should
also help to flesh out the differences between submodules and git-subtree.
Once the document is in good enough shape that it can be merged, it would be
easy enough to strip gitslave out if it were decided that it should not be
included.
>
> How about creating a topic branch for this and publishing it so several
> of us can collaborate? I think that would make things a bit easier
> moving forward.
I second that. As a git user, I would love to see a document that described
these systems, explaining how they differ, showing how various "common" actions
are done in each, and describing the workflows each is best in, and what
workflows each does poorly with.
If somebody does not create a branch and post a starting point, I'm afraid this
idea will simply die out.
--
username@localhost
next prev parent reply other threads:[~2012-04-28 17:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 9:27 organizing multiple repositories with dependencies Namit Bhalla
2012-04-16 14:30 ` Jakub Narebski
2012-04-16 20:08 ` dag
2012-04-17 17:29 ` Hilco Wijbenga
2012-04-17 17:51 ` dag
2012-04-17 18:37 ` Seth Robertson
2012-04-17 19:55 ` Hilco Wijbenga
2012-04-17 20:51 ` dag
2012-04-17 21:43 ` Hilco Wijbenga
2012-04-17 22:25 ` PJ Weisberg
2012-04-17 22:49 ` Hilco Wijbenga
2012-04-18 10:15 ` Namit Bhalla
2012-04-18 12:09 ` Jens Lehmann
2012-04-24 17:17 ` dag
2012-04-24 18:54 ` Hilco Wijbenga
2012-04-24 21:09 ` PJ Weisberg
2012-04-24 22:04 ` Hilco Wijbenga
2012-04-24 23:33 ` dag
2012-04-30 19:25 ` Phil Hord
2012-04-30 19:43 ` dag
2012-04-18 12:19 ` Jens Lehmann
2012-04-24 17:22 ` dag
2012-04-24 17:59 ` Seth Robertson
2012-04-24 20:26 ` Jens Lehmann
2012-04-24 20:52 ` Seth Robertson
2012-04-24 23:21 ` dag
2012-04-28 17:31 ` username localhost [this message]
2012-04-24 23:25 ` dag
2012-04-25 12:48 ` Seth Robertson
2012-04-27 14:23 ` dag
2012-04-24 19:48 ` Eugene Sajine
2012-04-24 22:11 ` Hilco Wijbenga
2012-04-24 23:38 ` dag
2012-04-24 23:36 ` dag
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=loom.20120428T191337-86@post.gmane.org \
--to=username.localhost@gmail.com \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).