Development mailing list

Hi, Am 23.04.2013 um 18:04 schrieb pulkomandy@xxxxxxxxxxxxx: On 2013-04-23 at 17:01:40 [+0200], Ingo Weinhold ingo_weinhold@xxxxxx wrote: 2. Potentially incompatible settings Not unheard of in ported software. Some kind of configuration file is required and the format respectively the default configuration changes. The package format could allow marking the file as mergeable for ...

On 04/23/2013 06:04 PM, pulkomandy@xxxxxxxxxxxxx wrote: On 2013-04-23 at 17:01:40 [+0200], Ingo Weinhold ingo_weinhold@xxxxxx wrote: 2. Potentially incompatible settings Not unheard of in ported software. Some kind of configuration file is ...

On 2013-04-23 at 17:01:40 [+0200], Ingo Weinhold ingo_weinhold@xxxxxx wrote: 2. Potentially incompatible settings Not unheard of in ported software. Some kind of configuration file is required and the format respectively the default configuration changes. The package format could allow marking the file as mergeable for simple text formats, in which case an attempt could be made to merge changes made by the user with those introduced by the newer version. ...

Greetings, I'd like to gather a few opinions and ideas wrt. how we want to handle settings (and similar) files in a package management context. Mainly this is about what shall happen with a software's settings files when said software is installed/uninstalled/updated. There are a few different kinds of settings files, which may need ...

Rene Gollent wrote: On 4/22/13, Siarzhuk Zharski zharik@xxxxxx wrote: I thought this subject-linking was surely buried a decade ago, but this idea looks like more viable than cockroaches. :-( Unfortunately, even gmail does this. Subject threading is blessed by the de-facto standard algorithm for email and usenet threading: ...

On April 22, 2013 at 11:37 PM Siarzhuk Zharski zharik@xxxxxx wrote: I thought this subject-linking was surely buried a decade ago, but this idea looks like more viable than cockroaches. :-( Just for statistic: my Thunderbird and my RoundCube are free of this problem. Unfortunately, this only works in a perfect world, where people do not reply to mails in order to write completely new mails to a mailing list, and where all mail clients actually support preserving the thread IDs. ...

On Mon, Apr 22, 2013 at 6:52 PM, Oliver Tappe zooey@xxxxxxxxxxxxxxx wrote: The subject should be fixed now, the subject now contains the short hash of the last commit (i.e. the current HEAD of that branch at the time), as suggested by John. Great, thanks so much! ...

On 4/22/13, Siarzhuk Zharski zharik@xxxxxx wrote: I thought this subject-linking was surely buried a decade ago, but this idea looks like more viable than cockroaches. :-( Unfortunately, even gmail does this. Regards, Rene ...

On 2013-04-22 at 23:04:02 [+0200], Jérôme Duval korli@xxxxxxxxxxxxxxxx wrote: 2013/4/22 John Scipione jscipione@xxxxxxxxx I've noticed that sometimes emails to haiku-commits will come looking like replies to the previous push instead of as a new email thread. I've discovered that this is because the new email affects identical components as the previous email which means that it also has an identical subject. For example this just happened with Ingo's few ...

Jérôme Duval писал 22.04.2013 23:04: 2013/4/22 John Scipione jscipione@xxxxxxxxx I've noticed that sometimes emails to haiku-commits will come looking like replies to the previous push instead of as a new email thread. I've discovered that this is because the new email affects identical ...

2013/4/22 John Scipione jscipione@xxxxxxxxx I've noticed that sometimes emails to haiku-commits will come looking like replies to the previous push instead of as a new email thread. I've discovered that this is because the new email affects identical components as the previous email which means that it also has an identical subject. For example this just happened with Ingo's few recent pushes concerning package management. ...

I've noticed that sometimes emails to haiku-commits will come looking like replies to the previous push instead of as a new email thread. I've discovered that this is because the new email affects identical components as the previous email which means that it also has an identical subject. For example this just happened with Ingo's few recent pushes concerning package management. Would it be possible to add some sort of unique identifier such as the short hash of the last commit to the email subject so that each email will be treated as a new thread? It's a small detail I know, but, it ...

Στις 22/4/2013 7:12 μμ, ο/η John Scipione έγραψε: On Mon, Apr 22, 2013 at 11:57 AM, Jérôme Duval korli@xxxxxxxxxxxxxxxx wrote: 2013/4/22 ΧΡΗΣΤΟΣ ΜΑΡΕΤΣΙΚΟΣ chrisgrelec@xxxxxx and then I open the text file mydumpfile with the program StyleEdit, I see for the dead key Rough breathing (Dasia)that it has 16 entries instead of 18. ...

On Mon, Apr 22, 2013 at 11:57 AM, Jérôme Duval korli@xxxxxxxxxxxxxxxx wrote: 2013/4/22 ΧΡΗΣΤΟΣ ΜΑΡΕΤΣΙΚΟΣ chrisgrelec@xxxxxx and then I open the text file mydumpfile with the program StyleEdit, I see for the dead key Rough breathing (Dasia)that it has 16 entries instead of 18. I don’t know who is the counter (or counters) in order to increase price from 16 to 18 entries when I make dump keymap. Not sure I understand what you mean. Would you mean 16 lines dumped instead ...

Hi, 2013/4/22 ΧΡΗΣΤΟΣ ΜΑΡΕΤΣΙΚΟΣ chrisgrelec@xxxxxx and then I open the text file mydumpfile with the program StyleEdit, I see for the dead key Rough breathing (Dasia)that it has 16 entries instead of ...