unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
* vim support improvements for 0.6
@ 2011-05-06 19:51 Jameson Graef Rollins
  2011-05-09 22:30 ` Felipe Contreras
  0 siblings, 1 reply; 3+ messages in thread
From: Jameson Graef Rollins @ 2011-05-06 19:51 UTC (permalink / raw)
  To: Felipe Contreras; +Cc: notmuch

[-- Attachment #1: Type: text/plain, Size: 695 bytes --]

Hi, Filipe.  I notice that you have been submitting a lot of patches for
vim support.  As you may have seen, I'm trying to put together a release
candidate for notmuch 0.6.  Since I know nothing about vim, would you be
willing to prepare a patch set that includes all of the patches to vim
support that you would like to see in the 0.6 release?

I think the easiest way to do that would be for you to push a branch to
your public repo that includes all of the vim improvements rebased on
top of my release-candidate/0.6 branch.  If you can then point me to
that branch, I can merge it with my release-candidate/0.6 branch and
push it out for others to test.

Let me know what you think.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: vim support improvements for 0.6
  2011-05-06 19:51 vim support improvements for 0.6 Jameson Graef Rollins
@ 2011-05-09 22:30 ` Felipe Contreras
  2011-05-10  9:14   ` Jameson Graef Rollins
  0 siblings, 1 reply; 3+ messages in thread
From: Felipe Contreras @ 2011-05-09 22:30 UTC (permalink / raw)
  To: Jameson Graef Rollins; +Cc: notmuch

On Fri, May 6, 2011 at 10:51 PM, Jameson Graef Rollins
<jrollins@finestructure.net> wrote:
> Hi, Filipe.  I notice that you have been submitting a lot of patches for
> vim support.  As you may have seen, I'm trying to put together a release
> candidate for notmuch 0.6.  Since I know nothing about vim, would you be
> willing to prepare a patch set that includes all of the patches to vim
> support that you would like to see in the 0.6 release?
>
> I think the easiest way to do that would be for you to push a branch to
> your public repo that includes all of the vim improvements rebased on
> top of my release-candidate/0.6 branch.  If you can then point me to
> that branch, I can merge it with my release-candidate/0.6 branch and
> push it out for others to test.
>
> Let me know what you think.

All right. Hopefully nobody will request further changes to these patches:
git://github.com/felipec/notmuch.git [fc-vim-next]

It's not rebased on top of your branch, but there are no merge conflicts.

Cheers.

-- 
Felipe Contreras

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: vim support improvements for 0.6
  2011-05-09 22:30 ` Felipe Contreras
@ 2011-05-10  9:14   ` Jameson Graef Rollins
  0 siblings, 0 replies; 3+ messages in thread
From: Jameson Graef Rollins @ 2011-05-10  9:14 UTC (permalink / raw)
  To: Felipe Contreras; +Cc: notmuch

[-- Attachment #1: Type: text/plain, Size: 399 bytes --]

On Tue, 10 May 2011 01:30:11 +0300, Felipe Contreras <felipe.contreras@gmail.com> wrote:
> All right. Hopefully nobody will request further changes to these patches:
> git://github.com/felipec/notmuch.git [fc-vim-next]
> 
> It's not rebased on top of your branch, but there are no merge conflicts.

Thanks, Felipe.  Merged with r-c/0.6 at
0e57911dae0dc07ae567fa4467a9686a9d090ace.

jamie.

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2011-05-10  9:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-05-06 19:51 vim support improvements for 0.6 Jameson Graef Rollins
2011-05-09 22:30 ` Felipe Contreras
2011-05-10  9:14   ` Jameson Graef Rollins

Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).