[Mesa-dev] abundance of branches in mesa.git
Steven Newbury
steve at snewbury.org.uk
Sun Feb 21 14:37:08 UTC 2016
On Sat, 2016-02-20 at 13:41 -0800, Jason Ekstrand wrote:
> On Feb 20, 2016 1:19 PM, "Rob Clark" <robdclark at gmail.com> wrote:
> >
> > fwiw, I think a *small* number of topic branches in certain cases
> > makes sense.. I'm definitely in support of a TTL limit (ie.
> > automatically nuke topic branches with no activity in N months, or
> > similar..)
>
> I agree. Sometimes something big comes up that's not ready for
> merging such
> as amdgpu or our recently pushed Vulkan driver. However, those
> should only
> be temporary and removed once the work is complete. I saw a
> "broadwell"
> branch in there which is probably at least 2 years old and completely
> subsumed by master. We don't want to be archiving random junk in the
> main
> tree.
>
> I'd be fine with a timeout system where non-release branches get the
> boot
> after a certain amount inactivity. If you want to archive something,
> that's
> what personal git repos are for.
> --Jason
>
I think it makes sense to have a publicly accessible archive repo for
nuked feature branches otherwise potentially useful code could just be
lost.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20160221/3d1e2979/attachment-0001.sig>
More information about the mesa-dev
mailing list