Re: path to gitlab upstream
- To: Geert Stappers <firstname.lastname@example.org>
- Cc: email@example.com
- Subject: Re: path to gitlab upstream
- From: Ian Jackson <firstname.lastname@example.org>
- Date: Sat, 2 Jun 2018 14:25:42 +0100
- Message-id: <[🔎] email@example.com>
- In-reply-to: <20180530131057.GN855@gpm.stappers.nl>
- References: <firstname.lastname@example.org> <20180525145223.GG21577@smithers.snow-crash.org> <email@example.com> <20180525170806.GH21577@smithers.snow-crash.org> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com> <20180530131057.GN855@gpm.stappers.nl>
Geert Stappers writes ("path to gitlab upstream"):
> There is https://gitlab.com/gitlab-org/gitlab-ce/
> It has currently 10,712 issues and 595 merge requests.
> About the issues: Open: 10,712 Closed: 25,941 All: 36,653
> MR: Open: 595 Merged: 15,906 Closed 2,696 All: 19,198
> That tells me that a Merge Request has a better success ratio.
> Also that it is wise to keep notes of the MR number :-/
I doubt it would be sensible for me to (probably incompetently)
reimplement the feature that the proprietary Gitlab EE has in this
area, and then send the result as an MR against Gitlab CE. It seems
more likely that enquiring politely in advance would be well-received.
Does anyone think I am wrong about that ?
Ian Jackson <firstname.lastname@example.org> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.