On Wed, 03 Feb 2010 22:58:05 -0500, Jameson Rollins
wrote:
> Once the project becomes more mature and other developers are
> vetting patches, then their branches can take over as "master" in the
> absence of an outdated canonical master.
The other thing that will happen as the project matures is
On Wed, 03 Feb 2010 22:58:05 -0500, Jameson Rollins wrote:
> Once the project becomes more mature and other developers are
> vetting patches, then their branches can take over as "master" in the
> absence of an outdated canonical master.
The other thing that will happen as the project matures is
On Wed, 27 Jan 2010 14:17:39 -0500, Ben Gamari wrote:
> I agree. There is no good reason to switch away from the existing
> infrastructure. If he wants, Carl can give regular contributors their
> own repositories on notmuchmail.org if some people have difficulties
> providing it themselves. After
On Wed, 27 Jan 2010 14:17:39 -0500, Ben Gamari wrote:
> I agree. There is no good reason to switch away from the existing
> infrastructure. If he wants, Carl can give regular contributors their
> own repositories on notmuchmail.org if some people have difficulties
> providing it themselves. After
also sprach Carl Worth [2010.02.04.1605 +1300]:
> > maint/? the stable release
> > master/ ? the stablising head
> > next/ ? testing branch
> > pu/ ? patch integration branch (proposed updates)
>
> I'm not a fan of this scheme, (or maybe I've just never quite understood
>
On Wed, 03 Feb 2010 19:05:42 -0800, Carl Worth wrote:
> I want to maintain a branch myself, (where I'm the only person pushing
> to the branch). [This is different than what I've done with the cairo
> repository where we have all core maintainer's pushing to a central
> repository. I'm intentional
On Wed, 03 Feb 2010 19:05:42 -0800, Carl Worth wrote:
> I want to maintain a branch myself, (where I'm the only person pushing
> to the branch). [This is different than what I've done with the cairo
> repository where we have all core maintainer's pushing to a central
> repository. I'm intentional
also sprach Carl Worth [2010.02.04.1605 +1300]:
> > maint/— the stable release
> > master/ — the stablising head
> > next/ — testing branch
> > pu/ — patch integration branch (proposed updates)
>
> I'm not a fan of this scheme, (or maybe I've just never quite understood
>
On Tue, 26 Jan 2010 10:32:31 +1300, martin f krafft wrote:
> I discussed this with Carl at LCA a bit and ideally we should come
> up with a way to relieve Carl of the bottleneck burden (obviously
> without stealing away his dictator hat ;)
Sounds great! Let's keep working together and find ways t
On Tue, 26 Jan 2010 10:32:31 +1300, martin f krafft
wrote:
> I discussed this with Carl at LCA a bit and ideally we should come
> up with a way to relieve Carl of the bottleneck burden (obviously
> without stealing away his dictator hat ;)
Sounds great! Let's keep working together and find ways
also sprach micah anderson [2010.01.27.1124 +1300]:
> Couldn't all of this be done without moving the existing git
> repository (don't forget that transition is a cost)? Those who
> wish to put together these proposed branches go ahead and do so,
> publishing those wherever they like (git.debian.o
* martin f krafft (madduck at madduck.net) wrote:
> also sprach micah anderson [2010.01.27.1124 +1300]:
> > Personally, I've found mailing lists that have patches sent to
> > them tends to totally kill the list for anything else. It seems
> > a bit weird to use Debian's bug tracker for a non-Debia
* martin f krafft (madd...@madduck.net) wrote:
> also sprach micah anderson [2010.01.27.1124 +1300]:
> > Personally, I've found mailing lists that have patches sent to
> > them tends to totally kill the list for anything else. It seems
> > a bit weird to use Debian's bug tracker for a non-Debian n
On Wed, 27 Jan 2010 11:24:15 +1300, micah anderson wrote:
> Couldn't all of this be done without moving the existing git repository
> (don't forget that transition is a cost)? Those who wish to put together
> these proposed branches go ahead and do so, publishing those wherever
> they like (git.de
Excerpts from micah anderson's message of Tue Jan 26 17:24:15 -0500 2010:
> On Mon, 25 Jan 2010 16:46:43 -0800, sebastian at sspaeth.de wrote:
> > > I think it would make sense to move the mainline to git.debian.org
> > > for now, or another place where everyone can easily get an account.
> > > As
also sprach micah anderson [2010.01.27.1124 +1300]:
> Couldn't all of this be done without moving the existing git
> repository (don't forget that transition is a cost)? Those who
> wish to put together these proposed branches go ahead and do so,
> publishing those wherever they like (git.debian.o
On Mon, 25 Jan 2010 16:46:43 -0800, sebastian at sspaeth.de wrote:
> > I think it would make sense to move the mainline to git.debian.org
> > for now, or another place where everyone can easily get an account.
> > As alternatives I propose repo.or.cz. I'd prefer to stay away from
> > commercial ser
On Wed, 27 Jan 2010 11:24:15 +1300, micah anderson wrote:
> Couldn't all of this be done without moving the existing git repository
> (don't forget that transition is a cost)? Those who wish to put together
> these proposed branches go ahead and do so, publishing those wherever
> they like (git.de
Excerpts from micah anderson's message of Tue Jan 26 17:24:15 -0500 2010:
> On Mon, 25 Jan 2010 16:46:43 -0800, sebast...@sspaeth.de wrote:
> > > I think it would make sense to move the mainline to git.debian.org
> > > for now, or another place where everyone can easily get an account.
> > > As alt
On Mon, 25 Jan 2010 16:46:43 -0800, sebast...@sspaeth.de wrote:
> > I think it would make sense to move the mainline to git.debian.org
> > for now, or another place where everyone can easily get an account.
> > As alternatives I propose repo.or.cz. I'd prefer to stay away from
> > commercial servic
also sprach Carl Worth [2010.01.23.1010 +1300]:
> Anyway, I'll be on vacation for the next few days, so will likely
> not have much, (likely have not much?), time for patch merging.
>
> But I *am* anxious to get back to the backlog. And in the
> meantime, I really appreciate others merging and sh
> I think it would make sense to move the mainline to git.debian.org
> for now, or another place where everyone can easily get an account.
> As alternatives I propose repo.or.cz. I'd prefer to stay away from
> commercial services like Github.
Any of those sounds fine to me, really. No preferences.
> I think it would make sense to move the mainline to git.debian.org
> for now, or another place where everyone can easily get an account.
> As alternatives I propose repo.or.cz. I'd prefer to stay away from
> commercial services like Github.
Any of those sounds fine to me, really. No preferences.
also sprach Carl Worth [2010.01.23.1010 +1300]:
> Anyway, I'll be on vacation for the next few days, so will likely
> not have much, (likely have not much?), time for patch merging.
>
> But I *am* anxious to get back to the backlog. And in the
> meantime, I really appreciate others merging and sh
On Fri, 22 Jan 2010 09:50:51 +0100, "Sebastian Spaeth" wrote:
> My feature-branch is still located here:
> http://github.com/spaetz/notmuch-all-feature
>
> So far things work fine for me. It would be cool if Carl would merge
> (parts of?) it.
Very much appreciated!
Thanks for putting this toget
On Fri, 22 Jan 2010 09:50:51 +0100, "Sebastian Spaeth"
wrote:
> My feature-branch is still located here:
> http://github.com/spaetz/notmuch-all-feature
>
> So far things work fine for me. It would be cool if Carl would merge
> (parts of?) it.
Very much appreciated!
Thanks for putting this toge
On Fri, 22 Jan 2010 09:09:30 +0100, Sebastian Spaeth
wrote:
> On 01/20/10 21:00, micah anderson wrote:
>
> > Cool! It would be useful if you provided thread-id's for each of these
> > so we could look them up and read more about them.
>
> True, I'll try to include thread id-s in the future.
I
On 01/20/10 21:00, micah anderson wrote:
> Cool! It would be useful if you provided thread-id's for each of these
> so we could look them up and read more about them.
True, I'll try to include thread id-s in the future.
spaetz
On Fri, 22 Jan 2010 09:09:30 +0100, Sebastian Spaeth
wrote:
> On 01/20/10 21:00, micah anderson wrote:
>
> > Cool! It would be useful if you provided thread-id's for each of these
> > so we could look them up and read more about them.
>
> True, I'll try to include thread id-s in the future.
I
On 01/20/10 21:00, micah anderson wrote:
Cool! It would be useful if you provided thread-id's for each of these
so we could look them up and read more about them.
True, I'll try to include thread id-s in the future.
spaetz
___
notmuch mailing list
n
On Wed, 20 Jan 2010 15:00:46 +0100, "Sebastian Spaeth"
wrote:
> As I do like some of the additional patches, I am shoving some of them
> into my "all feature" branch. I make that one available in case you
> want to pull from it. It currently carries:
>
> Jameson Rollins: Simplify "unread" tag h
On Wed, 20 Jan 2010 15:00:46 +0100, "Sebastian Spaeth" wrote:
> As I do like some of the additional patches, I am shoving some of them
> into my "all feature" branch. I make that one available in case you
> want to pull from it. It currently carries:
>
> Jameson Rollins: Simplify "unread" tag ha
As I do like some of the additional patches, I am shoving some of them
into my "all feature" branch. I make that one available in case you
want to pull from it. It currently carries:
Jameson Rollins: Simplify "unread" tag handling in emacs UI.
David Bremner: notmuch.el: Refactor citation markup. V
As I do like some of the additional patches, I am shoving some of them
into my "all feature" branch. I make that one available in case you
want to pull from it. It currently carries:
Jameson Rollins: Simplify "unread" tag handling in emacs UI.
David Bremner: notmuch.el: Refactor citation markup. V
34 matches
Mail list logo
