From: Eric Wong <e@80x24.org> To: Konstantin Ryabitsev <konstantin@linuxfoundation.org> Cc: meta@public-inbox.org Subject: Re: RFE: default hooks for git repositories Date: Mon, 1 Apr 2019 18:04:03 +0000 Message-ID: <20190401180403.o4zgowgyh3qq23iz@dcvr> (raw) In-Reply-To: <20190401154100.GA3701@chatter.qube.local> Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote: > On Mon, Mar 18, 2019 at 11:11:52PM +0000, Eric Wong wrote: > > Eric Wong <e@80x24.org> wrote: > > > Actually, is there a reason the git-native "init.templateDir" > > > configuration variable isn't sufficient? > > > > Ping? > > Sorry, Eric, I'm close to declaring email bankruptcy. :) I am okay with any > solution that lets us add hooks. To explain why we need hooks in > public-inbox repos, it's mostly for the ease of mirroring -- I want a > post-update hook to update the grokmirror [1] manifest so that our mirroring > script knows when there are updates and also when there are new archives or > repository epochs added. > > So, I defer to you entirely when it comes to how to do it. :) Yes, putting the hook in the init.templateDir should get you what you want. It would work the same for newly-created code repositories, too. > [1] https://github.com/mricon/grokmirror/ I should look into that for my own mirrors, even :)
next prev parent reply index Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-06 17:03 Konstantin Ryabitsev 2019-03-07 2:42 ` Eric Wong 2019-03-08 23:01 ` Eric Wong 2019-03-18 23:11 ` Eric Wong 2019-04-01 15:41 ` Konstantin Ryabitsev 2019-04-01 18:04 ` Eric Wong [this message] 2019-04-05 17:43 ` Konstantin Ryabitsev 2019-04-05 20:07 ` Eric Wong 2019-04-06 4:52 ` Eric Wong 2019-04-15 18:29 ` [PATCH] TODO: add an item for hooks support Eric Wong 2019-04-29 0:33 ` update on grokmirror integration [was: [PATCH] TODO: add an item for hooks support] Eric Wong
Reply instructions: You may reply publically to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://public-inbox.org/README * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190401180403.o4zgowgyh3qq23iz@dcvr \ --to=e@80x24.org \ --cc=konstantin@linuxfoundation.org \ --cc=meta@public-inbox.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
user/dev discussion of public-inbox itself Archives are clonable: git clone --mirror https://public-inbox.org/meta git clone --mirror http://czquwvybam4bgbro.onion/meta git clone --mirror http://hjrcffqmbrq6wope.onion/meta git clone --mirror http://ou63pmih66umazou.onion/meta Example config snippet for mirrors Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta nntp://news.gmane.org/gmane.mail.public-inbox.general note: .onion URLs require Tor: https://www.torproject.org/ AGPL code for this site: git clone https://public-inbox.org/public-inbox.git