From: Sebastian Tennant <sdt@sebyte.me>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: How to mirror and augment a git repository
Date: Sun, 05 Mar 2023 09:50:03 +0000 [thread overview]
Message-ID: <87mt4rcyt0.fsf@sebyte.me> (raw)
In-Reply-To: <143e4a36-02cc-d2a6-ff60-6b143d9e47b4@gmail.com> (Bagas Sanjaya's message of "Sun, 5 Mar 2023 16:02:05 +0700")
Quoth Bagas Sanjaya <bagasdotme@gmail.com>
on Sun, 5 Mar 2023 16:02:05 +0700:
> On 3/4/23 19:19, Sebastian Tennant wrote:
>> Hello list,
>>
>> I wish to mirror _and augment_ an upstream git repository.
>>
>> .--------.
>> |Upstream|
>> '--------'
>> |
>> .----------------.
>> |Augmented mirror|
>> '----------------'
>> / | \
>> .--------. .--------. .--------.
>> |Client#1| |Client#2| |Client#3|
>> '--------' '--------' '--------'
>>
>> Clients of the augmented mirror must have access to everything
>> available from upstream but must also be able to collaborate on
>> additional development branches not available from upstream.
>>
>
> I guess the augmented mirror is integration tree before changes
> from clients going upstream, right?
Some of the changes introduced by the clients may end up being
accepted upstream. The augmented mirror is primarily a way of
collaborating on and distributing customisations between clients.
next prev parent reply other threads:[~2023-03-05 9:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-04 12:19 How to mirror and augment a git repository Sebastian Tennant
2023-03-05 9:02 ` Bagas Sanjaya
2023-03-05 9:50 ` Sebastian Tennant [this message]
2023-03-06 8:08 ` Jeff King
2023-03-08 16:54 ` Sebastian Tennant
2023-03-09 3:12 ` Jeff King
2023-03-11 10:47 ` Sebastian Tennant
2023-03-11 14:55 ` Jeff King
2023-03-12 18:11 ` Sebastian Tennant
2023-03-13 16:30 ` Jeff King
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=87mt4rcyt0.fsf@sebyte.me \
--to=sdt@sebyte.me \
--cc=bagasdotme@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).