Zsh Mailing List Archive
Messages sorted by:
- X-seq: zsh-workers 41926
- From: Joey Pabalinas <alyptik@xxxxxxxxxxxxxx>
- To: "gi1242+zsh@xxxxxxxxx" <gi1242+zsh@xxxxxxxxx>
- Subject: Re: GH:zsh-users/zsh-completions.
- Date: Tue, 17 Oct 2017 17:09:50 -0400
- Cc: Peter Stephenson <p.stephenson@xxxxxxxxxxx>, Mailing-list zsh-workers <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=default; t=1508274592; bh=y8Y+ARoWKDnbe/MLtcFcaSQhflu0yY9C8F/1SbP7Z0w=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References: Feedback-ID:From; b=PS7UuXfu7FBHmSNj6cJQn8TnhS4LozzHYWZcFrEVzR4wjQvtdREzjgPNDz9BqkC4H 0YY8LyMqgSSXK9Rni91HWgwa8TReAGNo+r47GyR7ih9FTmW7VJa/8usvwt0Who/pvs QctiSJrYP0aPIojK0qaQsCsK9OSIhm8jUoNucKmE=
- Feedback-id: 8-0mGiMC4YahcjenscoyrfvJ_-bx5vIlqgi_hTVL6qTgzAkWhuaP7hy67RuH0jpsvQi4MN94N8aDIouUNjBAKg==:Ext:ProtonMail
- In-reply-to: <20171016174914.GO31613@andrew.cmu.edu>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:email@example.com>
- List-unsubscribe: <mailto:firstname.lastname@example.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <email@example.com> <CA+mcLN6ZuZ_AoKvfbceupZVg9+1btDg7NG=bGRUMDxwzLs5bcg@mail.gmail.com> <CGME20171016144130epcas1p2c1fa53d06d36c27f8ac8af3237b97721@epcas1p2.samsung.com> <firstname.lastname@example.org> <email@example.com> <CAH+w=7a2Y+hM_m22MCJYY=ZE67v-_PyOqqMkdC9c1JqCvbUAsg@mail.gmail.com> <firstname.lastname@example.org> <20171016174914.GO31613@andrew.cmu.edu>
- Reply-to: Joey Pabalinas <alyptik@xxxxxxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
On October 16, 2017 5:49PM UTC, GI <gi1242+zsh@xxxxxxxxx> wrote:
> > It's easy to have additional repositories at Sourceforge --- the
> > question is whether they can be set up conveniently for the desired
> > model, which I don"t know.
> If this is the path you are choosing, then take a look at "git
> subtrees". With this someone can simply clone the "whole source" and
> make changes anywhere (including completions), without even knowing
> there is a separate completion repository.
Although subtrees have their uses, in my opinion, uses them would result in
nearly the same issues as we are currently having.
Git subtrees lend themselves better when developing both main project
and sub-project within the same directory (a "system approach"). This, however,
would be more akin to a "vendor branch": a branch which allows you to access
a well-defined version of a vendor external component or VCS subdirectory, and
which is only updated with the new version of every release of that external
component. I often hear this referred to as a "component-approach", where the
*all* system is viewed as a collection of separate components developed on
In this case, we have a project and a sub-project with their own respective
lifecycles; neither of which are developed at the same rhythm, tagged together
at the same time, nor even tagged with the same name.
I feel like a good compromise would be for there to be a seperate, isolated
`zsh-completions` repository that both projects can submodule; this would
slightly relieve the pressures of trying to keep development rhythms in
sync, and will, in my opinion, make it simpler, not to mention much less
painful, to share changes between the two projects.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
Messages sorted by: