Would it be possible to associate a SSH Key with a specific git repo 
instead of only at the account level?

Depending on what this really means it could overlap with this thread.
<https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3CCEGEEBGIUEUS.2S2ZG4B0LCHZL%40taiga%3E#%3CCEH3AM4Q1JFV.GJHEVV2JNXIV@taiga%3E>
> git.sr.ht's ACL system doesn't really need to change and isn't part of
> this effort - rather, it's the model for this effort, if anything. The
> only change which is planned for git.sr.ht ACLs is support for adding
> permissions to specific SSH keys rather than for specific users.

Or maybe this request.
<https://lists.sr.ht/~sircmpwn/sr.ht-discuss/%3CCFBBCBC5-3A0E-45EF-BBDF-023FC9CC1763%40traduction-libre.org%3E>

Thanks.

"Robin Jarry" <robin@jarry.cc> writes:

>
> It looks like this should be handled by the email client itself.
> copy-to= should do something special depending on the account type. For
> imap/maildir, it only means saving the message in a folder. However for
> notmuch, it would require some additional steps. Maybe a completely
> different action.
>
> What do you think?
>

"Robin Jarry" <robin@jarry.cc> writes:

>
> It looks like this should be handled by the email client itself.
> copy-to= should do something special depending on the account type. For
> imap/maildir, it only means saving the message in a folder. However for
> notmuch, it would require some additional steps. Maybe a completely
> different action.
>
> What do you think?
>

On 2020-05-30 22:35, Jean-Christophe Helary wrote:
> 
> 
>> On Sun, 2020-05-31 at 09:49 +0900, Jean-Christophe Helary wrote:
>>> All the licenses that exist in the FOSS ecology are licenses that
>>> *protect* copyright. They don't make copyright weaker.
>>
>> Copyright needs no protection or clarification. Copyright is
>> automatically, immediately, and exclusively granted to an author when a
>> creative* work is fixed in a tangible form. Unless granted
>> permission/license by the author, no one has any right to distribute or
>> make copies of the work. No license protects or weakens copyright, per

On 2020-05-28 21:07, Drew DeVault wrote:
> I'm looking for user feedback on a set of proposed changes to the terms
> of service. You can read the full diff here:
> 
> 
> The short of it is that all public projects would be required to use
> licenses approved by the Free Software Foundation, Open Source
> Initiative, or Creative Commons, within 90 days of appearing on sr.ht.
> These changes, if we moved forward with them, would be announced 90 days
> in advance to give you ample time to deal with the changes as necessary
> for your projects.
> 

When viewing a message and after exiting pager (less) and going back to the message list a less process is left running for each message viewed.