Would patches introducing new git hooks, e.g. for post-fetch, be eligible for acceptance? If a more detailed explanation about a specific use case is required, I'd be happy to provide it.
Btw, the link in the README http://news.gmane.org/gmane.comp.version-control.git/ is dead.
Chiel
Jeff KingRe: Additional git hooks
On Thu, Dec 15, 2016 at 02:57:18PM +0100, Chiel ten Brinke wrote:
> Would patches introducing new git hooks, e.g. for post-fetch, be > eligible for acceptance?
The general guidelines for adding hooks is laid out here:
http://public-inbox.org/git/7vbq7ibxhh.fsf@gitster.siamese.dyndns.org/
-Peff
Jeff KingRe: Additional git hooks
On Thu, Dec 15, 2016 at 09:14:30AM -0500, Jeff King wrote:
> On Thu, Dec 15, 2016 at 02:57:18PM +0100, Chiel ten Brinke wrote: > > > Would patches introducing new git hooks, e.g. for post-fetch, be > > eligible for acceptance? > > The general guidelines for adding hooks is laid out here: > > http://public-inbox.org/git/7vbq7ibxhh.fsf@gitster.siamese.dyndns.org/
One interesting follow-up, though (which seems sensible to me):
http://public-inbox.org/git/7vr5fraxbf.fsf@alter.siamese.dyndns.org/
-Peff
Jeff King[PATCH] README: replace gmane link with public-inbox
On Thu, Dec 15, 2016 at 02:57:18PM +0100, Chiel ten Brinke wrote:
> Btw, the link in the README > http://news.gmane.org/gmane.comp.version-control.git/ is dead.
Yes, the status of gmane was up in the air for a while, but I think we can give it up as dead now (at least for our purposes).
-- >8 -- Subject: README: replace gmane link with public-inbox
The general status and future of gmane is unclear at this point, but certainly it does not seem to be carrying gmane.comp.version-control.git at all anymore. Let's point to public-inbox.org, which seems to be the favored archive on the list these days (and which uses message-ids in its URLs, making the links somewhat future-proof).
Reported-by: Chiel ten Brinke <ctenbrinke@gmail.com> Signed-off-by: Jeff King <peff@peff.net> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md index bd8a918a9..c0cd5580e 100644 --- a/README.md +++ b/README.md @@ -33,7 +33,7 @@ requests, comments and patches to git@vger.kernel.org (read [Documentation/SubmittingPatches][] for instructions on patch submission). To subscribe to the list, send an email with just "subscribe git" in the body to majordomo@vger.kernel.org. The mailing list archives are -available at http://news.gmane.org/gmane.comp.version-control.git/, +available at https://public-inbox.org/git, http://marc.info/?l=git and other archival sites. The maintainer frequently sends the "What's cooking" reports that
-- 2.11.0.348.g960a0b554
Re: [PATCH] README: replace gmane link with public-inbox
Jeff King <peff@peff.net> wrote:
> On Thu, Dec 15, 2016 at 02:57:18PM +0100, Chiel ten Brinke wrote: > > > Btw, the link in the README > > http://news.gmane.org/gmane.comp.version-control.git/ is dead. > > Yes, the status of gmane was up in the air for a while, but I think we > can give it up as dead now (at least for our purposes).
s/http/nntp/ still works for gmane.
> -- >8 -- > Subject: README: replace gmane link with public-inbox > > The general status and future of gmane is unclear at this > point, but certainly it does not seem to be carrying > gmane.comp.version-control.git at all anymore. Let's point > to public-inbox.org, which seems to be the favored archive > on the list these days (and which uses message-ids in its > URLs, making the links somewhat future-proof).
No objections, here.
There's also https://mail-archive.com/git@vger.kernel.org Where https://mid.mail-archive.com/<Message-ID> also works
Junio C HamanoRe: [PATCH] README: replace gmane link with public-inbox
Eric Wong <e@80x24.org> writes:
> Jeff King <peff@peff.net> wrote: > ... >> Yes, the status of gmane was up in the air for a while, but I think we >> can give it up as dead now (at least for our purposes). > > s/http/nntp/ still works for gmane. > ... >> -- >8 -- >> Subject: README: replace gmane link with public-inbox > ... > No objections, here. > > There's also https://mail-archive.com/git@vger.kernel.org > Where https://mid.mail-archive.com/<Message-ID> also works
Yes, but do we want to be exhaustive here, of just cite one that is a useful starting point? I think it is the latter.
Mentioning nntp for those who prefer (including me) may have value, though.
README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/README.md b/README.md index c0cd5580ea..91704fe451 100644 --- a/README.md +++ b/README.md @@ -34,7 +34,8 @@ requests, comments and patches to git@vger.kernel.org (read To subscribe to the list, send an email with just "subscribe git" in the body to majordomo@vger.kernel.org. The mailing list archives are available at https://public-inbox.org/git, -http://marc.info/?l=git and other archival sites. +http://marc.info/?l=git and other archival sites. +Those who prefer NNTP can use nntp://news.public-inbox.org/inbox.comp.version-control.git The maintainer frequently sends the "What's cooking" reports that list the current status of various development topics to the mailing