Andrei Alexandrescu, el 2 de August a las 10:16 me escribiste:
> On 2013-08-02 15:44:13 +0000, Leandro Lucarella said:
> >I'm not say is right or wrong for people to have this reflex of thinking
> >about multipliers, I'm just saying if you care about transmitting the
&
Walter Bright, el 30 de July a las 11:13 me escribiste:
> On 7/30/2013 2:59 AM, Leandro Lucarella wrote:
> >I just want to point out that being so much people getting this wrong
> >(and even fighting to convince other people that the wrong
> >interpretation is right) might
that the wrong
interpretation is right) might be an indication that the message you
wanted to give in that blog is not extremely clear :)
That was my whole point. If you used some easier measure to understand
(like using time instead of speed) you could have avoided all this
confusion :)
--
Leandro
Walter Bright, el 25 de July a las 18:33 me escribiste:
> On 7/25/2013 4:15 PM, Leandro Lucarella wrote:
> >Walter Bright, el 25 de July a las 14:27 me escribiste:
> >>On 7/25/2013 11:49 AM, Dmitry S wrote:
> >>>I am also confused by the numbers. What I see at the end
SomeDude, el 27 de July a las 20:27 me escribiste:
> On Friday, 26 July 2013 at 00:08:21 UTC, Leandro Lucarella wrote:
> >Walter Bright, el 25 de July a las 14:27 me escribiste:
> >>On 7/25/2013 11:49 AM, Dmitry S wrote:
> >>>I am also confused by the numbers. Wha
>really a 43% improvement. (Which is really great too.)
>
> 21.56/12.19 is 1.77, i.e. a >75% improvement in speed.
This is certainly misleading, is very easy to be confused with a time
reduction of 75%, which one would expect to be 1/4 of the original time.
:)
--
Leandro
Andrei Alexandrescu, el 23 de July a las 12:23 me escribiste:
> On 7/23/13 8:27 AM, Leandro Lucarella wrote:
> >You don't need push access to the blessed repository to contribute,
> >THAT's why git exists! Only people merging stuff needs push access and
> >is goo
l and needs to be expanded). Right now,
fortunately, the lack of review doesn't seem to be a huge bottleneck,
and while having committed, smart people helping could be beneficial,
I think is wise not to give every contributor push access to the repo
right now
e worded differently because one is in manpage format and the
other one in info/html/manual format.
http://www.gnu.org/software/coreutils/manual/html_node/echo-invocation.html
--
Leandro Lucarella (AKA luca) htt
John Colvin, el 7 de July a las 22:39 me escribiste:
> On Sunday, 7 July 2013 at 20:08:19 UTC, Leandro Lucarella wrote:
> >Andrei Alexandrescu, el 7 de July a las 09:06 me escribiste:
> >>On 7/7/13 8:55 AM, Andrei Alexandrescu wrote:
> >>>Here's a conf
og entry would become quite interesting.
If you want the specification, here it is :)
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/echo.html
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
-
if right now it would be
valuable to make the reference compiler partly closed.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
--
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145
are.
I'm just so glad that you are done with this debate... My eyes were
hurting from reading so much crap.
Bye, bye! Have fun with Visual C++!
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
-
Joakim, el 26 de June a las 17:52 me escribiste:
> On Wednesday, 26 June 2013 at 11:08:17 UTC, Leandro Lucarella wrote:
> >Joakim, el 25 de June a las 23:37 me escribiste:
> >>I don't know the views of the key contributors, but I wonder if
> >>they
> >>wou
Jacob Carlborg, el 26 de June a las 14:39 me escribiste:
> On 2013-06-26 12:16, Leandro Lucarella wrote:
>
> >Yeah, right, probably Python and Ruby have only 5k users...
>
> There are companies backing those languages, at least Ruby, to some
> extent.
Read my other post,
, probably Python and Ruby have only 5k users...
This argument is BS.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
--
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 94
bably just switch to gdc or ldc.
> This talk prominently mentioned scaling to a million users and being
> professional: going commercial is the only way to get there.
As in breaking into the commercial world? Then agreed. If you imply
commercial == closing some parts of the source, then I thin
drei
>
> Can you think of a better name than "D Summer Of Code"? It's very
> northern hemisphere centric and makes us southerners feel like the
> rest of the world doesn't know there is a southern hemisphere (or if
> they do that they don't know the
regressions introduced by
2.063 ;)
It certainly won't have new features or fixes for general bugs, but it
would be nice to have a changelog with the fixed regresssions.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
-
Jacob Carlborg, el 17 de June a las 12:42 me escribiste:
> On 2013-06-17 10:39, Regan Heath wrote:
>
> >Oh, yes, the ability to capture the compiler output and do a bit of a
> >parse and jump to error is another top IDE feature IMO.
>
> I have that in TextMate :)
S
Jacob Carlborg, el 14 de June a las 16:18 me escribiste:
> On 2013-06-14 15:37, Leandro Lucarella wrote:
>
> >I think, same as Manu said, if/when we were to move to D2 we'll have to
> >completely avoid
> >phobos unless a similar approach is taken in terms of mem
is taken in terms of memory allocation.
We even sometimes reuse exceptions to avoid allocating when something
throws.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
--
GPG Key: 5F5A8D05 (F
de the IDE crash consistently).
I think there a lot of working advanced editors for D, but IDEs are
quite behind (at least in Linux).
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
Hello there, a little late but you might enjoy it. It even
includes an exclusive interview with some of the speakers!
http://blog.sociomantic.com/2013/06/dconf-2013-review/
Feel free to share in all the usual social networks...
Walter Bright, el 31 de May a las 15:25 me escribiste:
> On 5/31/2013 2:52 PM, Leandro Lucarella wrote:
> >I think at some point I could be good to add a read-only *real* announce
> >list, so people only interested in knowing when a new release is
> >available don't have
ike this that have a lot of
traffic. This can also be easily covered by a RSS feed though.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
--
GPG Key: 5F5A8D05 (F8CD
Dicebot, el 31 de May a las 16:18 me escribiste:
> On Friday, 31 May 2013 at 14:08:18 UTC, Leandro Lucarella wrote:
> >>In mature projects RC does not differ that much from actual
> >>release
> >>other than by extra regression fixes. But for D process is not
> >
Dicebot, el 31 de May a las 16:21 me escribiste:
> On Friday, 31 May 2013 at 14:08:17 UTC, Leandro Lucarella wrote:
> >And I don't mean to minimize the incredible breakthrough
> >concerning the
> >release process in this cycle, just pointing out places were we
> >ca
Dicebot, el 31 de May a las 13:44 me escribiste:
> On Friday, 31 May 2013 at 09:08:17 UTC, Leandro Lucarella wrote:
> >This is just plain and completely wrong. I don't know many big-ish
> >opensource projects that doesn't have release candidates, and I
> >haven'
th the regressions that were fixed.
And I don't mean to minimize the incredible breakthrough concerning the
release process in this cycle, just pointing out places were we can
still do better :)
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
---
release.
This is just plain and completely wrong. I don't know many big-ish
opensource projects that doesn't have release candidates, and I haven't
see any "distribution" targeted at end users using release candidates.
Have you ever see a Linux distribution shipping an rc
the compiler almost
unusable). Maybe having something like a fixed weekly release of betas
would be a good idea. If one week there are no more bug reports against
the beta, then release that as the final version.
Betas are really release candidates, I think it might be a good idea to
just start
wesome.
I said it already in the beta ML, but I'll repeat it here. Awesome step
forward with the changelog, is extremely useful, exactly what
a developer updating the compiler want to see.
Thanks a lot!
--
Leandro Lucarella (AKA luca)
ade to the latest compiler.
That's completely FALSE. You might need some bugfixes! That view of "if
you want to be up to date you have to be willing to update a lot of
code" is really hurting D's stability.
--
Leandro Lucarella (AKA luca) http://llucax.com.
n. Also code review becomes a nightmare, when I see
immutable something = 1; I can't assume something will be always 1,
I have to take a look at the whole code looking for constructors. That
SUCKS.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
---
Is not sensible for code review. For me the price to pay for a feature
that add so little is too high. ROI ;)
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
--
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 54
native way to "fix" the potential deadlock
caused by glibc internal mutex).
> This approach does have the benefit that it will not cause pages
> that have been moved to swap to be pulled out in order to be scanned
> every time, though.
[1]
http://books.google.de/books/abou
Dicebot, el 21 de May a las 09:55 me escribiste:
> Can't wait to see a prototype for D2 :) I have a feeling that this
> may solve at least some of vibe.d latency issues at high concurrency
> levels.
I hope I can start porting it to D2 at some (not so far in the future)
point..
d memory using COW" in a context where fork() doesn't
happen? Why do you even need shared memory if fork() doesn't happen? If
"remap shared memory using COW" means get a different address for the
same block of memory until a write happens in that block, then you can't
s
deadalnix, el 16 de May a las 05:48 me escribiste:
> On Wednesday, 15 May 2013 at 20:08:23 UTC, Leandro Lucarella wrote:
> >OK, yeah, I thought I read 10 months somewhere and didn't do the
> >math
> >myself. 2.5 months is still high for my taste (and I insist, only
&g
Andrei Alexandrescu, el 14 de May a las 20:26 me escribiste:
> On 5/14/13 7:24 PM, Leandro Lucarella wrote:
> >Andrei Alexandrescu, el 11 de May a las 20:22 me escribiste:
> >>On 5/11/13 7:39 PM, Nick Sabalausky wrote:
> >>>Furthermore, my whole point was nothi
Steven Schveighoffer, el 14 de May a las 20:35 me escribiste:
> On Tue, 14 May 2013 20:26:36 -0400, Andrei Alexandrescu
> wrote:
>
> >On 5/14/13 7:24 PM, Leandro Lucarella wrote:
>
> >>Still, 10 months seems crazy. As
> >>somebody mentioned before, 1 month
Andrei Alexandrescu, el 14 de May a las 20:27 me escribiste:
> On 5/14/13 7:29 PM, Leandro Lucarella wrote:
> >Walter Bright, el 12 de May a las 11:42 me escribiste:
> >>On 5/12/2013 3:49 AM, John Colvin wrote:
> >>>As frustrating as it is for non-attending en
tations, and they each deserve their day
> in the sun. Spacing them out does that.
As a speaker, as I said before, what would make me happy is to make my
talk available as soon as possible. So, at least in my personal case,
the "day in the sun" argument doesn't apply :)
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
As
somebody mentioned before, 1 month seems much more reasonable, 2 at most.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
-header-non-affiliation
The problem is the D-ish amber stayed in the shadow for several years,
they didn't come up with the name just when it was made public.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
internals group? My emails always get
> bounced and I have to wait for someone to approve them.
Anyone can subscribe:
http://lists.puremagic.com/mailman/listinfo/dmd-internals
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
-
g approach. People need to learn how to do
a proper pull request, you can't get the committers doing cleaning work
after contributors. Is a learning process, once you get it right, your
pull requests shouldn't too many cycles to get accep
r
implementations with some official status!
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
--
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 94
David Nadlinger, el 18 de February a las 11:55 me escribiste:
> On Monday, 18 February 2013 at 10:07:58 UTC, Leandro Lucarella
> wrote:
> >Again, the problem is making the changelog update optional! No
> >pull
> >request should be merged if it doesn't include a proper
date the changelog when making
a pull request. That's it. You are making everything more complex than
it should be...
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
--
27;t be merged!
Making the changelog update go to just one person is the problem, that
work should be distributed and the better person to do it is the one
that made the change.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
-
g at some later point because
> they wanted to 'reopen' a bug.
+1 Having a "dynamic changelog" is a no-no. Is going against one of the
most basic properties of a changelog.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
--
he conf to make a script for some videos in form
> of wiki article.
If somebody make subtitles for the talks you could use this:
http://liliputing.com/2013/01/turn-subtitled-videos-into-ebooks-with-storyboard.html
:D
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
hat much. And then, as in C++, you have templates.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
--
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05)
-
cements written by others,
> too.)
Great. I think as a simple improvement to that, people willing to implement the
feature seriously, should assign themselves to the issue. This way the
"preapprovers" can see if there are any takes for the issue and prioritize
giving feedback to issue
uccessful.
And given how D community works, seems to make more sense to put
"Improvement Proposals" in bugzilla directly. The only drawback I see on
this is maybe big improvement proposals get less visibility and are not
easily differentiable from minor enhancements or even bugs.
--
r ages.
At this point I would be happy if we only get minor releases from time to time
fixing only regressions and critical/security bugs that can't wait for a next
release.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
Walter Bright, el 7 de January a las 13:27 me escribiste:
> On 1/7/2013 11:40 AM, Leandro Lucarella wrote:
> >Andrei Alexandrescu, el 7 de January a las 08:31 me escribiste:
> >>One thing I want to do is enshrine a vetting mechanism that would
> >>allow Walter
ove to D2
>
> 2. merge things from D2 into the D1 you've forked
What about licensing issues, is it even legal to for D1's backend? I mean, I
don't mind doing it personally, because I believe I won'
ally annoying us at work but I never got
to fix because the lack of feedback (a perfect example of somebody willing,
almost craving, to fix something and not doing it because of the lack of
feedback).
--
Leandro Lucarella (AKA luc
to define the feature with reasonable completeness
> before implementing it.
I think that would help a *LOT*. So basically this tag would mean
something like: If somebody implement this AND the implementation is
complete AND it has good quality, it will be in the next release?
If s
Brad Roberts, el 6 de January a las 17:28 me escribiste:
> On 1/6/2013 4:25 PM, Leandro Lucarella wrote:
> > I really hope at some point this will be addressed, and I think other
> > areas of the development process have been improved enough to think this
> > is a good momen
on the list would be solving the rvalue reference
> problem.
This is a good example of something that can go into a roadmap for the
next 1~3 months (AKA next release). See? You can do it. :P
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
to be convinced (or pushed) to do so. Maybe it will take 2
or 3 years.
Just as a history reminder, I wrote a rant a little more than 3 years
ago about things in the development process that needed to be addressed.
Now a lot of these issues have been addressed (or at least partially):
http://www.l
, that's another issue too. Having mutating "release notes" is awful
and a PR disaster. Users only see the changelog once, assuming is
immutable, because one thinks that releases are immutable and complete
(those are very fundamental properties of a release, otherwise is a
p
Walter Bright, el 4 de January a las 10:58 me escribiste:
> On 1/4/2013 6:02 AM, Leandro Lucarella wrote:
> >Walter Bright, el 3 de January a las 23:03 me escribiste:
> >>On 1/3/2013 9:49 PM, Jonathan M Davis wrote:
> >>>but other lines like
> >>>
>
y will be and a target date for the next
> >>release?
> >
> >We've never had a release that didn't have some new/changed features.
>
> I know.
>
> What I'm trying to see is what is the development *plan* for D2?
Plan? hahaha, you must be new around here
Jonathan M Davis, el 4 de January a las 08:12 me escribiste:
> On Friday, January 04, 2013 14:30:01 Leandro Lucarella wrote:
> > I think the best way to do it is to put it in the repository where the
> > changes were made (this implies having separate release notes for dmd,
Leandro Lucarella, el 4 de January a las 15:02 me escribiste:
> > Nothing has been deleted. In fact, I think those previous items in
> > the 2.060 New/Changed Features are seriously deficient because they
> > contain no hyperlinks for more information.
>
> This have t
Walter Bright, el 3 de January a las 22:34 me escribiste:
> On 1/3/2013 9:20 PM, Leandro Lucarella wrote:
> >Examples:
> >http://python.org/download/releases/3.3.0/
>
> I see a list, one line per, with a clickable link. The only real
> difference is that there's one
ly updated, badly.
I understand that, but I don't think that work should be optional and
only done if somebody feels like. Every pull request should include
proper documentation update. Can we try to focus on that for the next
release?
--
Leandro Lucarella (AKA luca)
ese notes together and
add them to the website. Even when doing it manually shouldn't be that
time consuming (is only copy&paste), this could also be automated.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
-
bug if it was
bothering me and want to know if it was fixed in this release.
What people will always read and care is the release announcement.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
--
GPG Key: 5F
Walter Bright, el 3 de January a las 19:18 me escribiste:
> On 1/3/2013 12:27 PM, Leandro Lucarella wrote:
> >BTW, Changelogs looks extremely naked now, I think release notes are
> >really needed now. Al least for new features. Is far from ideal to make
> >people go through
ature. Where would you put it? In the bug report itself? Most of the
time is not clear enough by the time the bug is created and the feature is
polished after a long discussion. You shouldn't make users go through the
entire history of a bug, which is completely internal to the compiler
develo
Iain Buclaw, el 3 de January a las 21:48 me escribiste:
> On 3 January 2013 20:27, Leandro Lucarella wrote:
>
> > Walter Bright, el 1 de January a las 15:46 me escribiste:
> > > The big news is Win64 is now supported (in alpha).
> > >
> > > htt
s).
Glad that the long waited new release is out, though, and the release
process is still improving :)
Happy new year to everyone!
[1] http://d.puremagic.com/issues/show_bug.cgi?id=7041
[2] https://github.com/D-Programming-Language/dmd/pull/1185
[3] https://github.com/D-Programming-Langu
bly start shipping minor releases. For
> example regression fixes in 2.061 in the next 2 weeks could be merged
> into the 2.061 branch as well and we could ship a 2.061.1 release with
> those fixes.
+1
Keepping a branch for each releas
ttps://bitbucket.org/larsivi/amber/wiki/Diff_D1
>
> I do not want to sound dismissive, but IMHO the list of differences
> is a bit "small" to start a new language..
The real difference is against D2, since D1 is considered a dead language
officially now. I think Amber tries
t; (not that comments wouldn't do the same).
>
> I don't believe those assertions to be true. Merging in either direction is
> possible and the difficulty lies in the
> nature of the drift between the two. Neither direction is necessarily any
> eas
An article that I think might be of interest for Phobos (I don't know how the
state of custom allocators is in phobos though).
http://www.yosefk.com/blog/why-custom-allocatorspools-are-hard.html
--
Leandro Lucarella (AKA luca) http://llucax.c
Jonathan M Davis, el 20 de November a las 14:45 me escribiste:
> On Tuesday, November 20, 2012 23:32:47 Paulo Pinto wrote:
> > Am 20.11.2012 21:57, schrieb Walter Bright:
> > > Since people already use precompiled headers with C++, I don't think
> > > this change has much chance of making it compil
Timon Gehr, el 14 de November a las 17:25 me escribiste:
> On 11/14/2012 03:31 PM, Leandro Lucarella wrote:
> >Tove, el 14 de November a las 13:55 me escribiste:
> >>>struct UserProfile {
> >>>@Id(1) i32 uid;
> >>>@Id(2) string name;
> >&g
Tove, el 14 de November a las 13:55 me escribiste:
> >struct UserProfile {
> >@Id(1) i32 uid;
> >@Id(2) string name;
> >@Id(3) string blurb;
> >}
> >
> >Where Id is "thrift.attributes.Id" or something similar.
>
> well, similar... but beginning with a symbol...
>
> [thrift.attributes.
Walter Bright, el 13 de November a las 16:49 me escribiste:
> On 11/13/2012 2:55 PM, bearophile wrote:
> >Walter Bright:
> >
> >>consider the type "int". Different modules impute different meanings into it
> >>all the time, and it doesn't cause terrible compatibility problems between
> >>modules.
>
Don Clugston, el 7 de November a las 09:23 me escribiste:
> >If you have no idea what my point is, I'm probably wasting my time
> >working on D.
>
> If you mean, we should be working on getting the existing stuff
> working before we think about adding more stuff, I agree 100%.
> I would say we're
Walter Bright, el 6 de November a las 20:19 me escribiste:
> On 11/6/2012 7:52 PM, bearophile wrote:
> >Walter Bright:
> >
> >>But I'm not sure at this point if that is the right thing to do.
> >
> >Why?
>
> D was fortunate in having 10 years of experience with C++'s
> exception system to learn f
he GC will "follow" the
pointer anyway. The array is allocated in a memory cell that would have
it's own type information and thus can be scanned (or ignored)
as needed.
--
Leandro Lucarella (AKA luca)
Leandro Lucarella, el 11 de October a las 00:34 me escribiste:
> Andrei Alexandrescu, el 10 de October a las 17:14 me escribiste:
> > On 10/10/12 4:29 PM, Leandro Lucarella wrote:
> > >I'm sorry to use this group to report this but I failed at looking for
> > >a
Andrei Alexandrescu, el 10 de October a las 17:14 me escribiste:
> On 10/10/12 4:29 PM, Leandro Lucarella wrote:
> >I'm sorry to use this group to report this but I failed at looking for
> >a better place to do so (including mailing Walter).
> >
> >The news.digitalm
there any way to get this fixed? Is there a better place to report
this kind of infrastructure problems?
Thanks.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
eeded one, I
> would use a struct.
Or even better, just use static import.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
--
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145 104C 949E BFB6 5F5A 8D05)
---
interrupt
the threads. I hope I can fix this problem eventually (the ideal for me
would be to find another way to pause the threads).
[1] http://www.dsource.org/projects/tango/browser/trunk/tango/core/rt/gc/cdgc
[2] http://www.llucax.com.ar/blog/blo
ll, free software[1] is closer to communism (or socialism), open
source (as in the OSD)[2] is closer to libertarianism.
"Open source is a development methodology; free software is a social
movement." -- Richard Stallman
[1] http://en.wikipedia.org/wiki/The_Free_Software_Definition
[2]
me script to pull the bug fixed from bugzilla.
Then you could edit that output manually if needed, preserving the
flexibility of the current approach.
--
Leandro Lucarella (AKA luca) http://llucax.com.ar/
---
ou're
new feature should be done already, the window is only there to say
"hey! Please pull from this branch!".
If you want a monthly release, I'd say a 1 week merge window is enough
(leaves you with 3 weeks for stabilization).
--
Leandro Lucarella (AKA luca)
a new branch or not push the
> changes upstream. Although I don't understand why Walter doesn't
> already do this.
The same reason he is pushing "revert ..." patches all the time, he is
using git as if it were svn :P
Adam Wilson, el 23 de July a las 11:07 me escribiste:
> On Mon, 23 Jul 2012 01:52:57 -0700, Leandro Lucarella
> wrote:
>
> >Adam Wilson, el 22 de July a las 16:05 me escribiste:
> >>I can't really say, but it sounds like what you are asking for is
> >>D2
re will
be enabled by default. Python 2.5.1 can only introduce bugfixes.
This is something I think D needs since ages ago[1], and I thought it was
finally here, but from what you say it doesn't like that way :S
[1]
http://www.llucax.com.ar/blog/blog/post/6cac01e1#source-control-and-versio
101 - 200 of 336 matches
Mail list logo
