On 29 March 2015, Nikolay Pavlov <[email protected]> wrote:
> 2015-03-29 18:56 GMT+03:00 Bram Moolenaar <[email protected]>:
> >
> > ZyX wrote:
> >
> > [...]
> >
> >> > > But the serious question:
> >> > >
> >> > > How will this work for syntax maintainers? In the past, we
> >> > > just send patches to the maintainers, who would then pass them
> >> > > along to you. Should we now send pull requests directly to the
> >> > > repo, and the maintainer can just vertify that it works?
> >> >
> >> > Nothing will change for now. Including syntax files is not
> >> > much work. Maintainers can make pull requests, but this still
> >> > requires generating an email to notify me (or someone else) and
> >> > very likely results in just getting the diff and including that.
> >> > Using the merge button on Github is not going to happen, it
> >> > results in my master version going out of sync.
> >>
> >> So, you are not going to receive emails from github? Github emails
> >> contains links to the generated diffs as well, they are kept in
> >> sync with the pull request.
> >
> > We could forward both issues and pull requests to the vim-dev list.
> > Like we currently do for issues on code.google.com. If this is too
> > spammy we can disable it.
>
> I am wondering whether it is possible to forward replies from vim-dev
> to github (*at least* when user does “Reply to all”).
If you reply to the notification messages from GitHub your reply is
posted to the issue tracker.
I don't know if you need to reply from the addres you're subscribed
from for that to work though. Does the GitHub tracker accept messages
form people without a GitHub account? It probably doesn't.
> With code.google.com issue tracker it was not uncommon situation when
> such forwarding resulted in discussion started in the issue tracker
> continued in vim-dev list where original author does not see it.
>
> Note that GH allows editing comments and original post itself both by
> author and by people with RW access. Edits are not sent to the user
> currently and I think they will neither be sent to the mailing list.
Both true.
> Also GH allows subscribing to the whole issue tracker. Thus *assuming
> used solution is the same as the former one with Google issue tracker*
> to avoid possible discussions that can be based on outdated posts and
> are not seen by some of the original authors (who are not subscribed
> here) it is better to either officially ban issue reports on vim-dev
> or disable issue tracker.
>
> Though I hope “reply all” reply will copy reply to GH avoiding the
> main problem.
/lcd
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
