about mercurial subrepo patches

Saint Germain saintger at gmail.com
Sun Feb 14 12:24:08 CST 2010


Hello,

2010/2/14 Martin Geisler <mg at lazybytes.net>:
> Saint Germain <saintger at gmail.com> writes:
>
>> Hello,
>>
>> It seems that Mercurial code freeze is about to begin (or is it
>> already done ?) and that my patches on subrepo have been more or less
>> forgotten ?
>
> They have not been forgotten, but I guess those that know about subrepos
> have been busy with other things. I have not yet spend time on subrepos,
> so I haven't commented on the patches.

Ok, I'm quite new to mercurial hacking so I don't understand how
mercurial developer keep track of all those patchs which arrive on the
mailing-list (good news ! a lot of contributors...).

> The feature freeze has begun, so we're only doing bug-fixes now. I just
> looked briefly at your patches, and from their description it sounds
> like they are indeed fixing bugs. So I think they can still go in.

Good news ! I don't know how I can help for them to go in ? I'm only
looking at my mailbox hoping some questions...

>> It's a pity because for us I think that they are essential to subrepo
>> (that's why I spent so much time trying to correct these issues),
>> maybe for other too ?
>
> Thank you for spending time on the patches!
>
> Releases in open source projects obey a rule similar to the Heisenberg
> uncertainty principle: you cannot both know which features a release
> will contain, and know when it will be released. You must either decide
> on the features and release "when it's ready", or you can decide on a
> release date and release with the features that happen to be ready at
> that date.
>
> We've chosen the latter with a regular schedule, so if your favorite
> feature doesn't make it for 1.5, then you'll have another chance in the
> next release cycle.
>

Ok I understand. Just let me know if you need me for those patches. I
have seen other bugs on subrepo (like the one with the 'push' which
should fail in case one of the subrepo 'push' fail) that I think I can
correct also. It's quite an achievement by the way, to have a code
clear enough that a beginner can start hacking without too much
trouble...

Thanks for your answer,


More information about the Mercurial-devel mailing list