On Thu, May 04, 2023 at 06:06:13PM +0200, Neels Hofmeyr wrote:
Should I change the way I do private branches in
osmocom?
I don't think so. Also, let's call them "personal branch" or
"developer branch"
rather than "private". As in fact, they are public, after all...
I push a lot of private branches everywhere. I was
asked in PM if I could cut
down on branches a bit because it clutters other developers' view of the git
history. My immediate response was: the other developer should simply not fetch
my branches, or invoke tig or gitk in a way that shows only selected branches.
exactly. you can always not fetch branches or do something like 'git branch -r | grep
-v neels'
if you don't want to see them.
For osmocom it apparently is mostly me pushing private
branches a lot. What if
we all did that...
I always push stuff that's WIP as a user branch.
In linux kernel development it seems to be more like
each developer has her own
public repository to make a mess in.
that's because they don't follow a model where anyone except a single developer
is
permitted to push to any branch within an entire repo. With gerrit/gitea/...
one can have more fine-grained permission models. And one also can have more
trust among a smaller group of developers, compared to the LK model where you have
thousands of developers.
So, i could make git clones of our main repositories
in gitea and keep my
private branches there.
Please don't. From my point of view it is critically important that I can see
whatever is happening. For example if somebody is on holidays or on sick leave,
it's great there is one designated place where all the latest work usually is.
At least for those people that regularly push their stuff, which should really
be everyone.
--
- Harald Welte <laforge(a)osmocom.org>
https://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)