You can remove the dormant convert. A new version is in the sandbox and
I doubt anything will be done with the dormant version.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 11/29/2013 8:24 AM, Christian Grobmeier wrote:
On 19.10. I wrote a mail in response to Henri Yandell.
htt
Gary Gregory wrote:
> I have partial interest in daemon and net because I use these at work or
> other project.
Then add yourself to the file ... that was the requested task in first place
;-)
- Jörg
>
> Gary
>
> Original message
> From: Benedikt Ritter
> Date:11/29/2013
On 2013-11-29, Bear Giles wrote:
> What are the license issues? I had looked at the legal stuff briefly
> but could have easily overlooked it since I was only looking at the
> tech note that documents their numerous versions.
Section 10 of the current APPNOTE.TXT:
10.1 The Use or Implementati
On 29 Nov 2013, at 19:21, sebb wrote:
I agree that the Javadoc pages could be removed.
Although it would not be difficult to fix the individual pages,
there's not much point in fixing Javadoc for dormant components.
However I'm not sure it makes sense to delete the entire website
because of the
I've been looking at the strong crypto side of it. I have a test file but the
published spec is vague at times (unless you are in windows and can use their
crypto library), not a huge hurdle but I've been busy. I should at least submit
a patch that recognizes the four addl block types even if we
On 29 November 2013 13:24, Christian Grobmeier wrote:
> On 19.10. I wrote a mail in response to Henri Yandell.
> http://markmail.org/message/c63kqyipuy6islib
>
> I would like to follow up on the issues i mentioned there.
>
> Our dormant components are unmaintained and our dormant websites are brok
On 11/28/13, 12:22 PM, Oliver Heger wrote:
>
> Am 28.11.2013 09:05, schrieb Thomas Neidhart:
>> On 11/28/2013 04:09 AM, Damjan Jovanovic wrote:
>>> Vote closed, results were:
>>>
>>> +1:
>>> Damjan Jovanovic
>>>
>>> No other votes were cast.
>>>
>>> Vote fails since majority approval needs at least
On 2013-11-29, dam6923 . wrote:
> I'm looking for the encryption that Windows XP provides for ZIP files.
> I believe it's the old, lame, encryption. Is that correct?
TBH, I have no idea. You may be able to tell by looking at the general
purpose bit of an encrypted entry. Bit 0 would be set whe
I'm looking for the encryption that Windows XP provides for ZIP files.
I believe it's the old, lame, encryption. Is that correct? Right
now I'm working with http://sevenzipjbind.sourceforge.net/ and it fits
the bill but is a bit clunky. Is that something that could be
accepted into ASF?
As alw
Le 29/11/2013 15:17, Christian Grobmeier a écrit :
> Lets say i have had good experiences with that model. I shared this
> information with you.
Thank you. And I discovered a tool to deal easily with topic branches.
The "git flow feature start/finish" syntax looks interesting.
> Do as you pleas
On 29 Nov 2013, at 14:44, Emmanuel Bourg wrote:
Le 29/11/2013 14:28, Christian Grobmeier a écrit :
We should respect the naming conventions of git as good as possible.
But git is a tool, not a development method, right? As such it doesn't
mandate any specific workflow, even if a random blogg
On 29 Nov 2013, at 14:39, Torsten Curdt wrote:
This in fact means:
create a master branch which is stable.
create a develop branch which is not so stable.
create feature branches from develop where you work out your
changes.
We are just swapping the branch names here, in the end your mod
Le 29/11/2013 14:28, Christian Grobmeier a écrit :
> We should respect the naming conventions of git as good as possible.
But git is a tool, not a development method, right? As such it doesn't
mandate any specific workflow, even if a random blogger chose to name
its own popular workflow "The Git
>
> This in fact means:
>>>
>>> create a master branch which is stable.
>>> create a develop branch which is not so stable.
>>> create feature branches from develop where you work out your changes.
>>>
>>
>> We are just swapping the branch names here, in the end your model isn't
>> very different f
I have partial interest in daemon and net because I use these at work or other
project.
Gary
Original message
From: Benedikt Ritter
Date:11/29/2013 05:36 (GMT-05:00)
To: Commons Developers List
Subject: Re: [CHALLENGE] Move All of Commons to the Dormant
2013/10/15 Hen
On 29 Nov 2013, at 14:09, Emmanuel Bourg wrote:
Le 29/11/2013 12:20, Christian Grobmeier a écrit :
This in fact means:
create a master branch which is stable.
create a develop branch which is not so stable.
create feature branches from develop where you work out your changes.
We are just sw
On 19.10. I wrote a mail in response to Henri Yandell.
http://markmail.org/message/c63kqyipuy6islib
I would like to follow up on the issues i mentioned there.
Our dormant components are unmaintained and our dormant websites are
broken.
Therefore I would like to remove the websites.
In example
Hi all,
Imaging uses a Map to pass parameters to the writers and
parsers. This isn't very convenient, because it's not immediately
obvious what parameters are available and what values are expected.
In constrast, javax.imageio has a hierarchy of parameter classes
(IIOParam, ImageReadParam, ImageW
Le 29/11/2013 12:20, Christian Grobmeier a écrit :
> This in fact means:
>
> create a master branch which is stable.
> create a develop branch which is not so stable.
> create feature branches from develop where you work out your changes.
We are just swapping the branch names here, in the end yo
On 26 Nov 2013, at 14:35, Gary Gregory wrote:
On Tue, Nov 26, 2013 at 3:52 AM, Emmanuel Bourg
wrote:
Le 26/11/2013 08:43, Benedikt Ritter a écrit :
I propose [1] as branching model. It looks very complicated at
first, but
I've found it very useful to always have a release ready version of
2013/10/15 Henri Yandell
> I contend that all of the Commons components are inactive and should move
> to the Attic/Dormant. In line with Phil's recent suggestion that anyone can
> present a dormancy challenge at any time, I'm challenging all of Commons
> Proper.
>
> I've made a file in SVN:
>
>
21 matches
Mail list logo
