Hi Nick,
Nick Dokos writes:
> But this is the second time that I have had to defend keeping the tag
> and I hope that the rest of you will sympathise with my reasons for
> keeping the tag.
Be reassured: at least I do. Hope we can move forward now.
--
Bastien
__
Matthew Sauer writes:
> I think that if it was kept as a single list the use of tags could allow (as
> long as people respect the tags) to filter and read only the types of
> threads they want to use.
>
> If we split the lists I would tag both with the same tag in my gmail box and
> read them all
On 28 Feb 2011, at 18:05, Samuel Wales wrote:
[O] is *much* better than [Orgmode]. Thank you.
Looking forward to [OD] and [OB], if that's what we will use.
Plus [OS], for discussions about splitting the mailing list.
Konrad
PS: Don't worry, this is my last post on this topic!
___
On Mon, Feb 28, 2011 at 10:14 AM, Nick Dokos wrote:
> Bastien wrote:
>
> > Julien Danjou writes:
> >
> > > On Mon, Feb 28 2011, Bastien wrote:
> > >> I changed the [Orgmode] tag to [O].
> > >
> > > Couldn't you just drop it?
> > >
> > > Seriously, this [O] is useless and ridiculous.
> >
> Not t
[O] is *much* better than [Orgmode]. Thank you.
Looking forward to [OD] and [OB], if that's what we will use.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo
Bastien wrote:
> Julien Danjou writes:
>
> > On Mon, Feb 28 2011, Bastien wrote:
> >> I changed the [Orgmode] tag to [O].
> >
> > Couldn't you just drop it?
> >
> > Seriously, this [O] is useless and ridiculous.
>
Not to me.
> No, it's useful to people who filter emails through the subject
The thing that is most difficult for me is the fact that I almost
never can read the entire subject header. Often I get to read only
the first word. Tags will make that worse.
I hope the switch from [Orgmode] to [O] will make things easier for you.
Since we now have a single letter [O] fo
On Mon, Feb 28 2011, Bastien wrote:
> No, it's useful to people who filter emails through the subject line.
It would be better to teach these people this is not a good practice
rather than polluting the subject lines for everybody…
--
Julien Danjou
❱ http://julien.danjou.info
pgpZrRQKSf1VX.pg
Julien Danjou writes:
> On Mon, Feb 28 2011, Bastien wrote:
>> I changed the [Orgmode] tag to [O].
>
> Couldn't you just drop it?
>
> Seriously, this [O] is useless and ridiculous.
No, it's useful to people who filter emails through the subject line.
--
Bastien
On Mon, Feb 28 2011, Bastien wrote:
> I changed the [Orgmode] tag to [O].
Couldn't you just drop it?
Seriously, this [O] is useless and ridiculous.
--
Julien Danjou
❱ http://julien.danjou.info
pgpcuBCMMMZGw.pgp
Description: PGP signature
___
Emacs
Dear all,
thanks all for your input.
Let's stick to one list for now, and let's try to use the [DEV] tag for
emails that only target development. It's not automatic and people will
forget sometimes, but on the overrall this will improve the readability
of the list, for both developers and users.
Samuel Wales writes:
> The thing that is most difficult for me is the fact that I almost
> never can read the entire subject header. Often I get to read only
> the first word. Tags will make that worse.
I hope the switch from [Orgmode] to [O] will make things easier for you.
--
Bastien
___
Hi Andrew,
"Andrew J. Korty" writes:
> It was suggested once that we shorten the [Orgmode] tag to [Org]. That
> seems like a change everyone can agree with. Could one of the mailing
> list admins please make that change?
I changed the [Orgmode] tag to [O].
This is short and unambiguous eno
Hi,
the same discussion was started a few month ago.
Basically, at that time there was quickly some argument to drop
[Orgmode] tag in the subject and try to reduce the tags to a certain amount.
Basically, I can't see any logical reason to keep [Orgmode] since this
is a org-mode list. Esp., nowad
On Mon, Feb 28, 2011 at 7:48 PM, Julien Danjou wrote:
> On Mon, Feb 28 2011, Alan L Tyree wrote:
>
> > The development list wouldn't be very interesting without the intense
> > interaction that it now has with users. The org list seems unique in
> > this, at least for the lists that I have someti
On Mon, Feb 28 2011, Alan L Tyree wrote:
> The development list wouldn't be very interesting without the intense
> interaction that it now has with users. The org list seems unique in
> this, at least for the lists that I have sometimes monitored.
No, really, it's not that unique. And many proje
Andrew J. Korty wrote:
> Alan L Tyree wrote:
>
> > I'm purely a user, but I would not be in favour of splitting the list.
> > I find it interesting to have an insight into what the developers are
> > doing, where org is headed. Use of a DEV tag would be good.
>
> I don't understand. If you l
I think that if it was kept as a single list the use of tags could allow (as
long as people respect the tags) to filter and read only the types of
threads they want to use.
If we split the lists I would tag both with the same tag in my gmail box and
read them all together, so it wouldn't really ap
On Sun, 27 Feb 2011 17:53:44 -0500
"Andrew J. Korty" wrote:
> Alan L Tyree wrote:
>
> > I'm purely a user, but I would not be in favour of splitting the
> > list. I find it interesting to have an insight into what the
> > developers are doing, where org is headed. Use of a DEV tag would
> > be
Alan L Tyree wrote:
> I'm purely a user, but I would not be in favour of splitting the list.
> I find it interesting to have an insight into what the developers are
> doing, where org is headed. Use of a DEV tag would be good.
I don't understand. If you like to read the development posts, why
The thing that is most difficult for me is the fact that I almost
never can read the entire subject header. Often I get to read only
the first word. Tags will make that worse.
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the
On Sun, Feb 27, 2011 at 4:20 PM, Jeff Horn wrote:
> If the lists were split, I likely would have never submitted my first
> patch. I've learned more about programming and computing from the
> org-mode list than any other list. I'm in favor of the status quo.
I fired off the e-mail before reading
If the lists were split, I likely would have never submitted my first
patch. I've learned more about programming and computing from the
org-mode list than any other list. I'm in favor of the status quo.
I make heavy use of mail tags. I almost always delete [PATCH] mails
immediately, and pay specia
On Sun, 27 Feb 2011 12:43:59 +0100
Bastien wrote:
> Hi Julien,
>
> Julien Danjou writes:
>
> > How about splitting the mailing list in a user and a development
> > list?
>
> I am in favor of using a [DEV] tag and stick to one single list.
>
> The path from users to developers (and to core Or
Even though I am not much into development I enjoy reading them as they are
teaching me about how this works and hopefully I can move to doing DEV
further down the road.
Even if we had two lists I would just add a filter tag like I do now and
sort them all into the same tag (well, maybe, maybe not
On Sun, Feb 27 2011, Bastien wrote:
> I am in favor of using a [DEV] tag and stick to one single list.
This is not something automatic, so this is not something everyone will
do. I won't think about it most of time and will forget, so…
> The path from users to developers (and to core Org develop
Hi Julien,
Julien Danjou writes:
> How about splitting the mailing list in a user and a development list?
I am in favor of using a [DEV] tag and stick to one single list.
The path from users to developers (and to core Org developers) is
a continuum, keeping this continuum on one list is a good
Hi,
There's really a lot of trafic here, and it's more and more diffcult to
me to follow development related threads in all the usage realted
threads.
How about splitting the mailing list in a user and a development list?
--
Julien Danjou
❱ http://julien.danjou.info
pgpy1t4BXGuu1.pgp
Descript
28 matches
Mail list logo
