Re: GitHub + notmuch scripts/hacks

William Casarin writes: > I've started collecting[1] a bunch of notmuch+GitHub hacks from some of > the discussions @ id:87d16jtsdj@kyleam.com > [..] > > [1] https://github.com/jb55/notmuch-github > [2] > https://github.com/jb55/notmuch-github/commit/fb2d80cf9ee9a5967c7

GitHub + notmuch scripts/hacks

Hey there, I've started collecting[1] a bunch of notmuch+GitHub hacks from some of the discussions @ id:87d16jtsdj@kyleam.com I've added the ability to comment on/approve/reject pull requests from a GitHub pull-request email[2]. It can also open a magit-log view of the PR from an email

Re: Washing GitHub emails to include inline patch?

Kyle Meyer writes: > Looking at what I wrote again, I'd change DONT-FETCH to FORCE-FETCH and > then do something like > > (when (or force-fetch > (not (magit-ref-exists-p local-ref))) > (magit-call-git "fetch" "origin")) > > where local-ref is bound to

Re: Washing GitHub emails to include inline patch?

William Casarin <j...@jb55.com> writes: > This worked pretty well, I've modified it a bit to support a generic > github repo location which is parsed from the subject, Great, glad you were able to tweak that test function into something that works well with your setup. > an

Re: Washing GitHub emails to include inline patch?

Kyle Meyer <k...@kyleam.com> writes: > --8<---cut here---start->8--- > > (defun km/notmuch-github-pr-number () > "Return the PR number for this message." > (let (pr) > (with-current-notmuch-show-message >

Re: Washing GitHub emails to include inline patch?

Kyle Meyer <k...@kyleam.com> writes: > Call M-x km/notmuch-visit-pr-in-magit in a notmuch-show buffer for a > GitHub PR, modifying km/notmuch-repo-from-message so that it returns > the full path to the local repository. Are you a wizard? That worked like magit. I changed km/n

Re: Washing GitHub emails to include inline patch?

William Casarin <j...@jb55.com> writes: > I now mainly review GitHub PRs via the patch fetching snippet you sent, > but there's a tedious disconnect between notmuch and magit. In the above > scenario, I would have to: > > 1. cd to the project > 2. open magit >

Re: Washing GitHub emails to include inline patch?

he commits locally to review/test. If I > regularly review PRs for a GitHub repo, I have > > fetch = +refs/pull/*/head:refs/pull/origin/* > > in the GitHub remote's configuration section of ".git/config". (GitLab > has an analogous merge request namespace.) Then,

Re: Washing GitHub emails to include inline patch?

nges, I want to apply the commits locally to review/test. If I regularly review PRs for a GitHub repo, I have fetch = +refs/pull/*/head:refs/pull/origin/* in the GitHub remote's configuration section of ".git/config". (GitLab has an analogous merge request namespace.) Then, after

Re: Washing GitHub emails to include inline patch?

Hey Kyle, Kyle Meyer <k...@kyleam.com> writes: >> I wonder if it would be be possible to wash this email by downloading >> the patch and present it inline like git-send-email. This would allow me >> to review patches without having to click around the GitHub inter

[github-thread] find and open corresponding github page for thread or message

Hi, this small script finds and opens the corresponding GitHub issue, comment, or pull-request. https://gist.github.com/gauteh/de546cb143ebae4a489a482a05ab4beb $ ./github-thread.py notmuch-thread-id [message-id] the first argument is always required. If a message id is specified

Re: Washing GitHub emails to include inline patch?

Kyle Meyer writes: > I have a command in my Emacs configuration that I think gets close to > what you want. This is great! Now if there was only a way to make it work for private repositories... hmm... -- https://jb55.com ___

Re: Washing GitHub emails to include inline patch?

Tomi Ollila <tomi.oll...@iki.fi> writes: > On Thu, Sep 21 2017, Kyle Meyer wrote: > >> >> --8<---cut here---start----->8--- >> (defun km/open-github-patch (buffer) >> "Find GitHub patch link in BUFFE

Re: Washing GitHub emails to include inline patch?

On Thu, Sep 21 2017, Kyle Meyer wrote: > > --8<---cut here---start->8--- > (defun km/open-github-patch (buffer) > "Find GitHub patch link in BUFFER and show it in a new buffer." > (let ((url > (with-curren

Re: Washing GitHub emails to include inline patch?

William Casarin writes: > Most of the patches I review these days comes in as GitHub emails that > look like this: > > > You can view, comment on, or merge this pull request online at: [...] > -- Patch Links -- > > https://github.com/monstercat/iris/pull/52.patch > ht

Washing GitHub emails to include inline patch?

Hey team, Most of the patches I review these days comes in as GitHub emails that look like this: --- Begin Message --- You can view, comment on, or merge this pull request online at: MIME-Version: 1.0 Content-Type: text/plain https://github.com/monstercat/iris/pull/52 -- Commit Summary

Re: Github an licensing

Mark Walters writes: >> On irc rlb pointed me to >> https://joeyh.name/blog/entry/removing_everything_from_github/ >> >> IANAL so I don't know whether it is a real problem, a hypothetical >> problem or not a problem. > > I got a couple of links sent to me privately

Re: Github an licensing

> On irc rlb pointed me to > https://joeyh.name/blog/entry/removing_everything_from_github/ > > IANAL so I don't know whether it is a real problem, a hypothetical > problem or not a problem. I got a couple of links sent to me privately which look relevant: *

Github an licensing

by people not responsible for the github mirror (*), but it might mean that those of us responsible for the mirror are illegally posting notmuch's code. Does anyone have any views on this, and whether we should carry on maintaining the github mirror? Best wishes Mark

Re: github mirror

for anyone interested and loosing the thread context) >> >> Marking this as notmuch::fixed as >> >> https://github.com/notmuch/notmuch >> >> fixes this and is usually up-to-date (I use this link on one of my >> notmuch installations) >> >> Interestin

Re: github mirror

s://github.com/notmuch/notmuch > > fixes this and is usually up-to-date (I use this link on one of my > notmuch installations) > > Interestingly the wiki is also in github (just that it is updated > March 28 -- based on https://github.com/notmuch ) Hi Tomi, My syncer for the wiki might have die

Re: github mirror

the wiki is also in github (just that it is updated March 28 -- based on https://github.com/notmuch ) Tomi On Sun, Apr 27 2014, Sam Halliday <sam.halli...@gmail.com> wrote: > Dear NotMuch, > > I have just started using notmuch and I really love it! I've been using &

[PATCH] doc: add README.md especially for github

On Fri, Oct 24 2014, David Bremner wrote: > Apparently README.md overrides README, so this will show up instead of > our generic README on github. > > If the user is already on github, then clicking a link for more > information is not a hardship. LGTM. although I'd prefer R

[PATCH] doc: add README.md especially for github

Tomi Ollila writes: > On Fri, Oct 24 2014, David Bremner wrote: > >> Apparently README.md overrides README, so this will show up instead of >> our generic README on github. >> >> If the user is already on github, then clicking a link for more >> information i

[PATCH] doc: add README.md especially for github

Apparently README.md overrides README, so this will show up instead of our generic README on github. If the user is already on github, then clicking a link for more information is not a hardship. --- README.md | 15 +++ 1 file changed, 15 insertions(+) create mode 100644 README.md

[PATCH] doc: add README.md especially for github

Apparently README.md overrides README, so this will show up instead of our generic README on github. If the user is already on github, then clicking a link for more information is not a hardship. --- README.md | 15 +++ 1 file changed, 15 insertions(+) create mode 100644 README.md

Re: [PATCH] doc: add README.md especially for github

On Fri, Oct 24 2014, David Bremner da...@tethera.net wrote: Apparently README.md overrides README, so this will show up instead of our generic README on github. If the user is already on github, then clicking a link for more information is not a hardship. LGTM. although I'd prefer

Re: [PATCH] doc: add README.md especially for github

Tomi Ollila tomi.oll...@iki.fi writes: On Fri, Oct 24 2014, David Bremner da...@tethera.net wrote: Apparently README.md overrides README, so this will show up instead of our generic README on github. If the user is already on github, then clicking a link for more information

github

Jameson Graef Rollins wrote: > On Mon, May 12 2014, Felipe Contreras wrote: > > How would our development cycle be controlled by GitHub? > > > > The whole point of a distributed VCS is that there isn't a single > > central repository you rely on. > > If this is

github

Jameson Graef Rollins writes: > On Mon, May 12 2014, Felipe Contreras wrote: >> How would our development cycle be controlled by GitHub? >> >> The whole point of a distributed VCS is that there isn't a single >> central repository you rely on. > > If this is

github

On Mon, May 12 2014, Felipe Contreras wrote: > How would our development cycle be controlled by GitHub? > > The whole point of a distributed VCS is that there isn't a single > central repository you rely on. If this is true then why are we even talking about github? jamie. ---

Re: github

On Mon, May 12 2014, Felipe Contreras felipe.contre...@gmail.com wrote: How would our development cycle be controlled by GitHub? The whole point of a distributed VCS is that there isn't a single central repository you rely on. If this is true then why are we even talking about github? jamie

Re: github

Jameson Graef Rollins jroll...@finestructure.net writes: On Mon, May 12 2014, Felipe Contreras felipe.contre...@gmail.com wrote: How would our development cycle be controlled by GitHub? The whole point of a distributed VCS is that there isn't a single central repository you rely

Re: github

Jameson Graef Rollins wrote: On Mon, May 12 2014, Felipe Contreras felipe.contre...@gmail.com wrote: How would our development cycle be controlled by GitHub? The whole point of a distributed VCS is that there isn't a single central repository you rely on. If this is true then why

github

On Mon, May 12, 2014 at 9:30 PM, Jameson Graef Rollins wrote: > On Sun, Apr 27 2014, Jani Nikula wrote: >> To be honest, I am slightly concerned by the popularity of >> github. Despite being a hosting site primarily for open source, it *is* >> a proprietary platform. Source

github

On Sun, Apr 27 2014, Jani Nikula wrote: > To be honest, I am slightly concerned by the popularity of > github. Despite being a hosting site primarily for open source, it *is* > a proprietary platform. Source code hosting is plain git, but AFAIK all > the rest (review process, is

Re: github

On Sun, Apr 27 2014, Jani Nikula j...@nikula.org wrote: To be honest, I am slightly concerned by the popularity of github. Despite being a hosting site primarily for open source, it *is* a proprietary platform. Source code hosting is plain git, but AFAIK all the rest (review process, issue

Re: github

On Mon, May 12, 2014 at 9:30 PM, Jameson Graef Rollins jroll...@finestructure.net wrote: On Sun, Apr 27 2014, Jani Nikula j...@nikula.org wrote: To be honest, I am slightly concerned by the popularity of github. Despite being a hosting site primarily for open source, it *is* a proprietary

Github?

On Sat, May 10 2014, "Wael M. Nasreddine" wrote: > On Fri, May 9, 2014 at 6:21 PM, David Bremner wrote: >> Felipe Contreras writes: >> >>> Amadeusz ?o?nowski wrote: The same goes for Travis. There's already a build bot. Why bother with Travis? >>> >>> I've never seen any buildbot

Github?

Felipe Contreras writes: > Amadeusz ?o?nowski wrote: >> The same goes for Travis. There's already a build bot. Why bother >> with Travis? > > I've never seen any buildbot results. TravisCI's interface is just > simple and easy. And all it requires is one file. > Not to take a position on

Github?

Tomi Ollila wrote: > BTW: does .travis.yml support comment lines ? It's YAML. So, yes. -- Felipe Contreras

Re: Github?

On Sat, May 10 2014, Wael M. Nasreddine wael.nasredd...@gmail.com wrote: On Fri, May 9, 2014 at 6:21 PM, David Bremner da...@tethera.net wrote: Felipe Contreras felipe.contre...@gmail.com writes: Amadeusz Żołnowski wrote: The same goes for Travis. There's already a build bot. Why bother

Re: Github?

Tomi Ollila wrote: BTW: does .travis.yml support comment lines ? It's YAML. So, yes. -- Felipe Contreras ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch

Github?

On Fri, May 9, 2014 at 6:21 PM, David Bremner wrote: > Felipe Contreras writes: > >> Amadeusz ?o?nowski wrote: >>> The same goes for Travis. There's already a build bot. Why bother >>> with Travis? >> >> I've never seen any buildbot results. TravisCI's interface is just >> simple and easy. And

Submodules for language bindings (was: Github?)

On Fri, May 09, 2014 at 07:40:27AM -0500, Felipe Contreras wrote: > Suvayu Ali wrote: > > > To explain my point with RPM specifics, if I were to > > use separate spec files, python-notmuch would have: > > > > Requires: notmuch >= > > > > As you can see this only allows for tracking

Github?

Hi, Wael Nasreddine writes: > I was a bit disappointed that the project is not living (or at least > mirrored) to Github, it would have made my search much easier. How GitHub would help with this? I believe that most of search engines reach Notmuch home page. GitHub is not the

Submodules for language bindings (was: Github?)

Hi Trevor, On Thu, May 08, 2014 at 04:35:30PM -0700, W. Trevor King wrote: > On Fri, May 09, 2014 at 12:45:27AM +0200, Suvayu Ali wrote: > > On Thu, May 08, 2014 at 03:29:31PM -0700, W. Trevor King wrote: > > > On Fri, May 09, 2014 at 12:00:46AM +0200, Suvayu Ali wrote: > > > > One of my TODOs is

Github?

h you, >> otherwise I'll just remove everything): >> >> - Revert my changes (except for the CI) >> - Set a cron job to update the mirror hourly for the Github user wanting to >> fork. >> - Remove the Issues, Pull Request and the Wiki >> - Add a "m

Submodules for language bindings (was: Github?)

Suvayu Ali wrote: > On Fri, May 09, 2014 at 07:40:27AM -0500, Felipe Contreras wrote: > > Suvayu Ali wrote: > > > > > To explain my point with RPM specifics, if I were to > > > use separate spec files, python-notmuch would have: > > > > > > Requires: notmuch >= > > > > > > As you can see

Submodules for language bindings (was: Github?)

Suvayu Ali wrote: > You have a point, however I would still disagree. You seem to use > Gentoo, and I think what you say works better for Gentoo because it is > a source distribution. For binary distributions, this is a bit harder > (and limiting). No, it's not harder. > To explain my point

Github?

e everything): > > - Revert my changes (except for the CI) > - Set a cron job to update the mirror hourly for the Github user wanting to > fork. > - Remove the Issues, Pull Request and the Wiki > - Add a "mirror of .." to the description on top of the page > - Manually update th

Github?

Amadeusz ?o?nowski wrote: > The same goes for Travis. There's already a build bot. Why bother > with Travis? I've never seen any buildbot results. TravisCI's interface is just simple and easy. And all it requires is one file. -- Felipe Contreras

Github?

u, May 08, 2014 at 11:18:23PM +, Wael Nasreddine wrote: > > > Well like I said in my first email, if you guys are interested in > owning > > > and maintaining the GitHub repo it is yours, besides I have not done > > > anything with the history I only

Submodules for language bindings (was: Github?)

On Thu, May 08, 2014 at 03:29:31PM -0700, W. Trevor King wrote: > On Fri, May 09, 2014 at 12:00:46AM +0200, Suvayu Ali wrote: > > One of my TODOs is to also package the ruby bindings, and > > notmuch-vim. The only thing preventing me now is my unfamiliarty > > with ruby, and Fedora packaging

Github?

I understand. Maybe we should convert the current Github to a real mirror, mirroring all the branches and tags as is and a) add .Travis.yml upstream or b) maintain a separate fork (maybe under my own profile) for Travis integration Would you be willing to add Travis.yml upstream? In any case

Github?

On Thu, May 08, 2014 at 08:01:56PM -0700, W. Trevor King wrote: > Agreed. The only problem I'd have is that you'd want to say that the > GitHub repo was a mirror, since the primary repo would still be > git://notmuchmail.org/git/notmuch. If it's a mirror, I think it > should mir

Github?

On Thu, May 08, 2014 at 11:21:00PM +0200, guyzmo wrote: > On Thu, May 08, 2014 at 10:30:19PM +0200, Suvayu Ali wrote: > > On Thu, May 08, 2014 at 01:14:51PM -0700, Wael M. Nasreddine wrote: > > > On Thu, May 8, 2014 at 12:54 PM, Wael Nasreddine > > > wrote: > [...] > > > Can you guys at least

Github?

On Thu, May 08, 2014 at 10:30:19PM +0200, Suvayu Ali wrote: > On Thu, May 08, 2014 at 01:14:51PM -0700, Wael M. Nasreddine wrote: > > On Thu, May 8, 2014 at 12:54 PM, Wael Nasreddine > > wrote: [...] > > Can you guys at least consider splitting contrib/ and bindings/ into their > > own repo? It

Github?

Well like I said in my first email, if you guys are interested in owning and maintaining the GitHub repo it is yours, besides I have not done anything with the history I only added one commit which will never conflict with upstream unless you add a .Travis.yml file :) On Thursday, May 8, 2014 3

Re: Submodules for language bindings (was: Github?)

Hi Trevor, On Thu, May 08, 2014 at 04:35:30PM -0700, W. Trevor King wrote: On Fri, May 09, 2014 at 12:45:27AM +0200, Suvayu Ali wrote: On Thu, May 08, 2014 at 03:29:31PM -0700, W. Trevor King wrote: On Fri, May 09, 2014 at 12:00:46AM +0200, Suvayu Ali wrote: One of my TODOs is to also

Re: Github?

Hi, Wael Nasreddine wael.nasredd...@gmail.com writes: I was a bit disappointed that the project is not living (or at least mirrored) to Github, it would have made my search much easier. How GitHub would help with this? I believe that most of search engines reach Notmuch home page. GitHub

Re: Github?

Amadeusz Żołnowski wrote: The same goes for Travis. There's already a build bot. Why bother with Travis? I've never seen any buildbot results. TravisCI's interface is just simple and easy. And all it requires is one file. -- Felipe Contreras ___

Re: Submodules for language bindings (was: Github?)

Suvayu Ali wrote: You have a point, however I would still disagree. You seem to use Gentoo, and I think what you say works better for Gentoo because it is a source distribution. For binary distributions, this is a bit harder (and limiting). No, it's not harder. To explain my point with

Re: Submodules for language bindings (was: Github?)

On Fri, May 09, 2014 at 07:40:27AM -0500, Felipe Contreras wrote: Suvayu Ali wrote: To explain my point with RPM specifics, if I were to use separate spec files, python-notmuch would have: Requires: notmuch = version-string As you can see this only allows for tracking dependency

Re: Submodules for language bindings (was: Github?)

Suvayu Ali wrote: On Fri, May 09, 2014 at 07:40:27AM -0500, Felipe Contreras wrote: Suvayu Ali wrote: To explain my point with RPM specifics, if I were to use separate spec files, python-notmuch would have: Requires: notmuch = version-string As you can see this only

Re: Github?

Felipe Contreras felipe.contre...@gmail.com writes: Amadeusz Żołnowski wrote: The same goes for Travis. There's already a build bot. Why bother with Travis? I've never seen any buildbot results. TravisCI's interface is just simple and easy. And all it requires is one file. Not to take a

Re: Github?

On Fri, May 9, 2014 at 6:21 PM, David Bremner da...@tethera.net wrote: Felipe Contreras felipe.contre...@gmail.com writes: Amadeusz Żołnowski wrote: The same goes for Travis. There's already a build bot. Why bother with Travis? I've never seen any buildbot results. TravisCI's interface is

Github?

the CI) > > - Set a cron job to update the mirror hourly for the Github user wanting > > to fork. > > - Remove the Issues, Pull Request and the Wiki > > - Add a "mirror of .." to the description on top of the page > > - Manually update the contrib/ bindings

Github?

Wael Nasreddine wrote: > Actually you can't have the .Travis.yml file in a separate branch, > Travis require it present in the context that it is testing (commits > to all branches) Yes, so? The 'travis-ci' branch can merge from upstream, and then upstream would be tested. -- Felipe Contreras

Github?

guyzmo wrote: > do you know about git submodules? It's actually there to be able to > track changes on remote repositories that are closely related, > while keeping a sane separation. Git sumobules are more like a hack than an integral part of Git. I personally avoid them like the plague.

Github?

Wael Nasreddine wrote: > Would you be willing to add Travis.yml upstream? I would. After all we have packaging stuff which are not strictly part of notmuch. -- Felipe Contreras

Github?

W. Trevor King wrote: > On Thu, May 08, 2014 at 11:18:23PM +, Wael Nasreddine wrote: > > Well like I said in my first email, if you guys are interested in owning > > and maintaining the GitHub repo it is yours, besides I have not done > > anything with the history I only a

Github?

Wael Nasreddine wrote: > Well like I said in my first email, if you guys are interested in > owning and maintaining the GitHub repo it is yours, besides I have not > done anything with the history I only added one commit which will > never conflict with upstream unless you add a .Tra

Github?

On Thu, May 08, 2014 at 09:43:01PM -0500, Felipe Contreras wrote: > W. Trevor King wrote: > > I don't think merge conflicts are the problem here. If the GitHub > > mirror claims to be a mirror but adds an additional commit B? > > That wouldn't be a problem if HEAD di

Github?

(except for the CI) - Set a cron job to update the mirror hourly for the Github user wanting to fork. - Remove the Issues, Pull Request and the Wiki - Add a "mirror of .." to the description on top of the page - Manually update the contrib/ bindings/ as they change in here and maybe automat

Github?

On Fri, May 09, 2014 at 12:13:51AM +, Wael Nasreddine wrote: > I understand. Maybe we should convert the current Github to a real mirror, > mirroring all the branches and tags as is and a) add .Travis.yml upstream > or b) maintain a separate fork (maybe under my own profile) f

Github?

On Thu, May 08, 2014 at 11:18:23PM +, Wael Nasreddine wrote: > Well like I said in my first email, if you guys are interested in owning > and maintaining the GitHub repo it is yours, besides I have not done > anything with the history I only added one commit which will never

Submodules for language bindings (was: Github?)

On Fri, May 09, 2014 at 12:45:27AM +0200, Suvayu Ali wrote: > On Thu, May 08, 2014 at 03:29:31PM -0700, W. Trevor King wrote: > > On Fri, May 09, 2014 at 12:00:46AM +0200, Suvayu Ali wrote: > > > One of my TODOs is to also package the ruby bindings, and > > > notmuch-vim. The only thing

Submodules for language bindings (was: Github?)

On Fri, May 09, 2014 at 12:00:46AM +0200, Suvayu Ali wrote: > One of my TODOs is to also package the ruby bindings, and > notmuch-vim. The only thing preventing me now is my unfamiliarty > with ruby, and Fedora packaging guidelines for ruby-gems. I think this is one argument argument in favor of

Github?

Wael M. Nasreddine wrote: > Can you guys at least consider splitting contrib/ and bindings/ into > their own repo? It don't think that's such a good idea. One of the reasons Notmuch and other projects like the Linux kernel have everything under one tree is that changes in the API can be done

Github?

On Thu, May 08, 2014 at 07:54:38PM +, Wael Nasreddine wrote: > - Revert my changes (except for the CI) I'd revert all the changes and submit them upstream, so the GitHub repository is an exact mirror of http://git.notmuchmail.org/git/notmuch. A Travis-CI file is Travis-speci

Github?

ptable with you, > otherwise I'll just remove everything): > > - Revert my changes (except for the CI) > - Set a cron job to update the mirror hourly for the Github user wanting > to fork. > - Remove the Issues, Pull Request and the Wiki > - Add a "mirror of .." to t

Github?

Hi, On Thu, May 08, 2014 at 09:40:45AM +0100, Eric wrote: > On Thu, 08 May 2014 09:13:56 +0200, Jani Nikula wrote: > > On Thu, 08 May 2014, Wael Nasreddine wrote: [...] > >> Any thoughts on moving to Github? > > http://mid.gmane.org/87wqea7c37.fsf at nikula.org > Exac

Github?

> Great, thanks for your interest in notmuch! > >> I was a bit disappointed that the project is not living (or at least >> mirrored) to Github, it would have made my search much easier. Meaning that you start with the idea that everything should be in Github??? >> Any thought

Github?

On Thu, 08 May 2014, Wael Nasreddine wrote: > I forgot to mention that I also enabled Travis-CI for notmuch, you can > access it here , there are 33 failed > tests, they are also failing on my own machine. Apparently the test suite does not handle missing

Github?

te: > Hello everyone, > > Thank you so much for creating Notmuch, I am coming from sup and I was > looking for a more stable alternative and I think I found what I am looking > for :) > > I was a bit disappointed that the project is not living (or at least > mirrored) to Githu

Github?

Hello everyone, Thank you so much for creating Notmuch, I am coming from sup and I was looking for a more stable alternative and I think I found what I am looking for :) I was a bit disappointed that the project is not living (or at least mirrored) to Github, it would have made my search much

Re: Github?

that the project is not living (or at least mirrored) to Github, it would have made my search much easier. Any thoughts on moving to Github? http://mid.gmane.org/87wqea7c37@nikula.org I took the liberty of making the first move by creating https://github.com/notmuch and splitting

Re: Github?

On Thu, 08 May 2014, Wael Nasreddine wael.nasredd...@gmail.com wrote: I forgot to mention that I also enabled Travis-CI for notmuch, you can access it here https://travis-ci.org/notmuch/notmuch, there are 33 failed tests, they are also failing on my own machine. Apparently the test suite does

Re: Github?

Hi, On Thu, May 08, 2014 at 09:40:45AM +0100, Eric wrote: On Thu, 08 May 2014 09:13:56 +0200, Jani Nikula j...@nikula.org wrote: On Thu, 08 May 2014, Wael Nasreddine wael.nasredd...@gmail.com wrote: [...] Any thoughts on moving to Github? http://mid.gmane.org/87wqea7c37@nikula.org

Re: Github?

(except for the CI) - Set a cron job to update the mirror hourly for the Github user wanting to fork. - Remove the Issues, Pull Request and the Wiki - Add a mirror of .. to the description on top of the page - Manually update the contrib/ bindings/ as they change in here and maybe automate it later

Re: Github?

acceptable with you, otherwise I'll just remove everything): - Revert my changes (except for the CI) - Set a cron job to update the mirror hourly for the Github user wanting to fork. - Remove the Issues, Pull Request and the Wiki - Add a mirror of .. to the description on top of the page

Re: Github?

On Thu, May 08, 2014 at 07:54:38PM +, Wael Nasreddine wrote: - Revert my changes (except for the CI) I'd revert all the changes and submit them upstream, so the GitHub repository is an exact mirror of http://git.notmuchmail.org/git/notmuch. A Travis-CI file is Travis-specific

Re: Github?

for the Github user wanting to fork. - Remove the Issues, Pull Request and the Wiki - Add a mirror of .. to the description on top of the page - Manually update the contrib/ bindings/ as they change in here and maybe automate it later. Can you guys at least consider splitting contrib

Re: Github?

Wael M. Nasreddine wrote: Can you guys at least consider splitting contrib/ and bindings/ into their own repo? It don't think that's such a good idea. One of the reasons Notmuch and other projects like the Linux kernel have everything under one tree is that changes in the API can be done across

Re: Github?

On Thu, May 08, 2014 at 10:30:19PM +0200, Suvayu Ali wrote: On Thu, May 08, 2014 at 01:14:51PM -0700, Wael M. Nasreddine wrote: On Thu, May 8, 2014 at 12:54 PM, Wael Nasreddine wael.nasredd...@gmail.comwrote: [...] Can you guys at least consider splitting contrib/ and bindings/ into their

Re: Github?

On Thu, May 08, 2014 at 11:21:00PM +0200, guyzmo wrote: On Thu, May 08, 2014 at 10:30:19PM +0200, Suvayu Ali wrote: On Thu, May 08, 2014 at 01:14:51PM -0700, Wael M. Nasreddine wrote: On Thu, May 8, 2014 at 12:54 PM, Wael Nasreddine wael.nasredd...@gmail.comwrote: [...] Can you guys

Submodules for language bindings (was: Github?)

On Fri, May 09, 2014 at 12:00:46AM +0200, Suvayu Ali wrote: One of my TODOs is to also package the ruby bindings, and notmuch-vim. The only thing preventing me now is my unfamiliarty with ruby, and Fedora packaging guidelines for ruby-gems. I think this is one argument argument in favor of

Re: Github?

everything): - Revert my changes (except for the CI) - Set a cron job to update the mirror hourly for the Github user wanting to fork. - Remove the Issues, Pull Request and the Wiki - Add a mirror of .. to the description on top of the page - Manually update the contrib/ bindings

Re: Submodules for language bindings (was: Github?)

On Thu, May 08, 2014 at 03:29:31PM -0700, W. Trevor King wrote: On Fri, May 09, 2014 at 12:00:46AM +0200, Suvayu Ali wrote: One of my TODOs is to also package the ruby bindings, and notmuch-vim. The only thing preventing me now is my unfamiliarty with ruby, and Fedora packaging guidelines

  1   2   >