Re: [Savannah-hackers-public] git over https

2017-02-09 Thread James Cloos 
> "BP" == Bob Proulx  writes:

BP> Thorsten Glaser poked us in relation to deprecating the cvs pserver
BP> support to use anonymous ssh (traditionally anoncvs) for this type of
BP> access.  See https://www.openbsd.org/papers/anoncvs-slides.pdf .  What
BP> would you think of using anonymous instead?  I think that would be a
BP> superior way to go.

The best way to do anonymous ssh is to publish a well-known async key (I
suggest the null ed25519 key) and tell users to use that to achieve read-
only anon ssh access.

But for git everyone else does smart-git over https.  Sv SHOULD, too.

-JimC
-- 
James Cloos  OpenPGP: 0x997A9F17ED7DAEA6

Re: [Savannah-hackers-public] bzr post-commit email hook

2017-02-09 Thread Glenn Morris 

Here are the bzr notes from a few years ago, which may or not still be useful:

https://lists.gnu.org/archive/html/savannah-hackers-public/2013-06/msg00042.html

It should basically be the bzr-email plugin, yes.

[Savannah-hackers-public] git commit mails seem missing

2017-02-09 Thread Simon Goldschmidt 
Hi folks,

 

I just noticed I didn't get commit mails from yesterday's pushes to the lwip-commit list. The archive http://lists.nongnu.org/archive/html/lwip-commits/ also doesn't list them. The last mails in there are from 2 days ago (feb 7).

 

Cheers,

Simon

Re: [Savannah-hackers-public] bzr post-commit email hook (was: gsrc-commit auto messages stopped working)

2017-02-09 Thread carl hansen 
On Wed, Feb 8, 2017 at 9:39 PM, Bob Proulx  wrote:

> Hello Carl,
>
> carl hansen wrote:
> > still still not working
>
> Sorry there has been delays.  We have been overwhelmed trying to
> juggle too many things.
>
> ​I know the feeling. Luckily it doesn't matter.
​


> I would love to help fix your hook problem.  But I enter this knowing
> nothing about bzr.  I've never used bzr before.  I poke into your bzr
> repository and explore.
>
>   vcs:/srv/bzr/gsrc# grep -rl gsrc-commit .
> ./trunk/.bzr/branch/branch.conf
>
>   vcs:/srv/bzr/gsrc# cat ./trunk/.bzr/branch/branch.conf
> last_revision_mailed = bran...@invergo.net-20130610174455-
> orqjagls9tgp1noq
> post_commit_to = gsrc-com...@gnu.org
> post_commit_body = ""
> post_commit_subject = $nick r$revision: $message
>
> Okay.  That seems to be the configuration for it.  But how does that
> even do anything?  I was expecting to see a hooks directory or
> something.  Searching the web for documentation on setting up bzr
> hooks did not yield anything useful to me.
>
> Do you know how hook scripts with bzr work?  Perhaps you can help me
> help you.
>
> Bob
>
​Ok I am poking around.
​$  bzr help hooks
spits out some text including:
"post_commit
~~~
Introduced in: 2.0
Called after a commit is performed on a tree. The hook is called with
a bzrlib.mutabletree.PostCommitHookParams object. The mutable tree the
commit was performed on is available via the mutable_tree attribute of
that object."