This is the mail archive of the
mailing list for the glibc project.
Re: glibc git commit hooks update.
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: DJ Delorie <dj at redhat dot com>
- Cc: "Carlos O'Donell" <codonell at redhat dot com>, libc-alpha at sourceware dot org
- Date: Mon, 15 Apr 2019 22:22:30 +0200
- Subject: Re: glibc git commit hooks update.
- References: <firstname.lastname@example.org>
* DJ Delorie:
> For the benefit of those of us who aren't git-savvy, could you please
> summarize what a long-term in-branch development process should look
> like? I.e. one that's optimal for our new configuration on sourceware?
> I recall going through that with the tcache work, constantly merging
> master into the branch, flooding irc, messing up my local repo, and I
> recall it was... suboptimal.
You can do whatever you want on the private branches. IRC, email,
Bugzilla updates are all disabled as of today.
In theory, too many private branches could cause repository bloat, but
given the amount of history we carry around anyway, I don't expect
this to be a substantial issue.