Stefan Sperling wrote on Mon, 16 Nov 2009 at 14:39 +0100:
> Julian asked for a formal description of how 'svn patch' applies
> hunks. Below are my current plans. The current code does something
> quite different and will be changed to implement what is described
> below before 1.7 release.
Okay, g
The ASF mailer splits big mails up into multiple mails?! That's the coolest
thing. Ever. Loove.
--
C. Michael Pilato
CollabNet <> www.collab.net <> Distributed Development On Demand
Dunno. Lots of java packages have had to deal with the issue as they
migrate to the ASF. I'm sure that gene...@incubator (cc'd) has some
prior knowledge and precedent.
Cheers,
-g
On Mon, Nov 16, 2009 at 11:47, C. Michael Pilato wrote:
> What does the migration mean for JavaHL's package namespace
On Mon, Nov 16, 2009 at 11:52 AM, Hyrum K. Wright
wrote:
>
> On Nov 16, 2009, at 10:49 AM, Mark Phippard wrote:
>
>> On Mon, Nov 16, 2009 at 11:47 AM, C. Michael Pilato
>> wrote:
>>> What does the migration mean for JavaHL's package namespace and our version
>>> compatibility?
>>
>> If we change
Stefan Sperling wrote:
> See subject. Just a reminder for whoever has the means to configure
> our project at cia.vc.
This reminds me: I've updated the project's OhLoh enlistments, too.
--
C. Michael Pilato
CollabNet <> www.collab.net <> Distributed Development On Demand
signature.a
On Nov 16, 2009, at 10:49 AM, Mark Phippard wrote:
> On Mon, Nov 16, 2009 at 11:47 AM, C. Michael Pilato
> wrote:
>> What does the migration mean for JavaHL's package namespace and our version
>> compatibility?
>
> If we change the package names we would break all users. So I would
> say it m
On Mon, Nov 16, 2009 at 11:47:56AM -0500, C. Michael Pilato wrote:
> What does the migration mean for JavaHL's package namespace and our version
> compatibility?
Aren't the package names just convention?
What's wrong with just keeping to use org.tigris?
The designers of Java could not have been as
On Mon, Nov 16, 2009 at 11:47 AM, C. Michael Pilato wrote:
> What does the migration mean for JavaHL's package namespace and our version
> compatibility?
If we change the package names we would break all users. So I would
say it means we cannot change the names.
--
Thanks
Mark Phippard
http:/
What does the migration mean for JavaHL's package namespace and our version
compatibility?
--
C. Michael Pilato
CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
Julian asked for a formal description of how 'svn patch' applies
hunks. Below are my current plans. The current code does something
quite different and will be changed to implement what is described
below before 1.7 release.
Any feedback appreciated.
Stefan
This note is a high-level description
See subject. Just a reminder for whoever has the means to configure
our project at cia.vc.
Stefan
11 matches
Mail list logo