On Mo, 24 Aug 2015, Alejandro Exojo wrote:
El Monday 24 August 2015, Christian Brabandt escribió:
I am not going to start rewriting mails, that are sent from github. It's
just a simple forwarding, since the original github notification mail is
rejected by the google groups page.
Note
Am 2015-08-27 06:35, schrieb LCD 47:
On 26 August 2015, Christian Brabandt cbli...@256bit.org wrote:
[...]
Also I added an Mail-Followup-To header, so depending on the reply
method you use, a reply might end up at github as well (which needs to
be tested).
[...]
Does Outlook pay attention
On 26 August 2015, Christian Brabandt cbli...@256bit.org wrote:
[...]
Also I added an Mail-Followup-To header, so depending on the reply
method you use, a reply might end up at github as well (which needs to
be tested).
[...]
Does Outlook pay attention to Mail-Followup-To these days? Does
On Di, 25 Aug 2015, tux. wrote:
Yes, the newest patch is tagged on Bitbucket, but I don't get it :/
Did you run hg pull -u?
BTW: What is this?
To: Christian Brabandt vim_dev@googlegroups.com
Best,
Christian
--
Der Religion ist nur das Heilige wahr,
der Philosophie nur das Wahre heilig.
Christian Brabandt schrob am Dienstag, 25. August 2015 um 19:26 Zeit:
Did you run hg pull -u?
Yes, but it did not change a thing. -- However, I (seem to) have found
my mistake: I had local changes, mostly leftovers from the old
repository. Thanks, I seem to have the right versions now.
BTW:
On 2015-08-25, tux. wrote:
BTW: Having my local hg repository set to Bitbucket and typing hg
pull does *not* pull the newest tags, it's still at 7.4.826 for me :/
I just did that (2015-08-25 17:03Z) and retrieved through 7.4.836.
vim/.hg/hgrc:
default =
BTW: Having my local hg repository set to Bitbucket and typing hg
pull does *not* pull the newest tags, it's still at 7.4.826 for me :/
--
--
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
Am 2015-08-25 04:06, schrieb Marvin Renich:
* Christian Brabandt cbli...@256bit.org [150824 16:28]:
On Mo, 24 Aug 2015, Marvin Renich wrote:
(I have set up an forwarding of all notifications from the vim
repository to the vim-dev ml).
I have started getting mail from Vim Github Repository
On Mo, 24 Aug 2015, Marvin Renich wrote:
(I have set up an forwarding of all notifications from the vim
repository to the vim-dev ml).
I have started getting mail from Vim Github Repository; apparently
they are pull-requests forwarded to vim-dev. I have two problems with
this mail. First
I have started getting mail from Vim Github Repository; apparently
they are pull-requests forwarded to vim-dev. I have two problems with
this mail. First, the person who sent the PR isn't identified. (This
was also a problem with the Vim problem tracker.)
Second, the List-ID headers
* Christian Brabandt cbli...@256bit.org [150824 16:28]:
On Mo, 24 Aug 2015, Marvin Renich wrote:
(I have set up an forwarding of all notifications from the vim
repository to the vim-dev ml).
I have started getting mail from Vim Github Repository; apparently
they are pull-requests
El Monday 24 August 2015, Christian Brabandt escribió:
I am not going to start rewriting mails, that are sent from github. It's
just a simple forwarding, since the original github notification mail is
rejected by the google groups page.
Note that the sender name is lost as well. It's
12 matches
Mail list logo
