[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Access to push new branch to origin
From: |
Werner LEMBERG |
Subject: |
Re: Access to push new branch to origin |
Date: |
Sat, 23 May 2020 15:01:11 +0200 (CEST) |
> I can grant you access to the repository later today if needed.
> However I'd first like to understand (probably from Werner) what
> makes a branch in the upstream repository more "preserving" than a
> public clone. Being distributed it really doesn't make much
> difference from the git perspective.
IMO, code for a LilyPond GSoC project should become an integral part
of the master git repository. I think it should be freezed in its
final form (this is, right after GSoC ends) for documentation
purposes. If the stuff gets merged, the branch should still stay and
not be deleted.
Note that this is my personal point of view, and I don't insist on it.
On the other hand: if you see problems with that approach please
elaborate.
Werner
- Access to push new branch to origin, Owen Lamb, 2020/05/22
- Re: Access to push new branch to origin, Jonas Hahnfeld, 2020/05/23
- Re: Access to push new branch to origin,
Werner LEMBERG <=
- Re: Access to push new branch to origin, Urs Liska, 2020/05/23
- Re: Access to push new branch to origin, Jonas Hahnfeld, 2020/05/23
- Re: Access to push new branch to origin, Jonas Hahnfeld, 2020/05/25
- Re: Access to push new branch to origin, Urs Liska, 2020/05/25
- Re: Access to push new branch to origin, Jonas Hahnfeld, 2020/05/25