On 09/12/2019 16:26, ajs6f wrote:
I'm not sure why I would want to use a clunky and less-functional (no reply-to
to comment on PR, non-formatting-aware) email list instead of the more
powerful_and_ more pleasant GH system.
No one is asking you to.
It is not either-or.
GH tools remain
> On Dec 9, 2019, at 10:01 AM, Andy Seaborne wrote:
> The important point is a less-busy dev@.
Well, I want the right discussion on dev@, not just less discussion. Now that I
go back and look over the recent archives, it's not clear to me at all that if
we drop all the duplication we are now
On 09/12/2019 13:26, ajs6f wrote:
For pr@, reply-to is dev@ (same as commits@) - PR discussion is done on GH so
the usual GH controls work for people. pr@ is more of a safe archive.
GH notifications include the ability to reply via email to put a remark in the
conversation. How will
strangepleasures commented on issue #646: JENA-1785: A newly created node can
remain invisible after commit
URL: https://github.com/apache/jena/pull/646#issuecomment-563255055
Sure
This is an automated message from the
afs commented on issue #646: JENA-1785: A newly created node can remain
invisible after commit
URL: https://github.com/apache/jena/pull/646#issuecomment-563245118
Good idea.
If you update the PR, we are ready to put this in.
I'll go and update/clean up the comments once it's
>>> For pr@, reply-to is dev@ (same as commits@) - PR discussion is done on GH
>>> so the usual GH controls work for people. pr@ is more of a safe archive.
GH notifications include the ability to reply via email to put a remark in the
conversation. How will that work with this? IMO, that is
+1 This change seems like it will make my life easier so I am in favor ;)
On Mon, Dec 9, 2019 at 11:48 AM Andy Seaborne wrote:
>
>
> On 05/12/2019 14:12, Andy Seaborne wrote:
> > Now would be a good time to get this done so we can have dev@ for
> > discussions.
> >
> > Please yes/no/etc and
On 05/12/2019 14:12, Andy Seaborne wrote:
Now would be a good time to get this done so we can have dev@ for
discussions.
Please yes/no/etc and when it settles down I'll run a vote.
Ping?
When going to infra, we then have a definite PMC agreement to point to,
not some minority or rogue
afs opened a new pull request #648: JENA-1793: Decode %-encoded UTF-8
URL: https://github.com/apache/jena/pull/648
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
Andy Seaborne created JENA-1793:
---
Summary: IRILib.decode does not reverse encoded UTF-8
Key: JENA-1793
URL: https://issues.apache.org/jira/browse/JENA-1793
Project: Apache Jena
Issue Type:
10 matches
Mail list logo
