[development] A streamlined way to develop core patches

[Matt V.]

I realize this thread is a bit old, but I ran across it in the archives and
decided to create the documentation page Chris described:

    http://drupal.org/node/355154

I was able to track down two mirrors each in Subversion, Git, and Bazaar. If
anyone knows of a Mercurial mirror (or any other additions or corrections),
please feel free to update the page.

- Matt V.


Chris Johnson-21 wrote:
> 
> Should we have a handbook page or two on drupal.org which lists the
> currently supported alternative repositories, and brief summaries of
> their usage (i.e. copy the Four Kitchens description above essentially
> verbatim)?  It seems like services like these could be highly valuable
> to the community.
> 
> Thanks to all who support these things.
> 
> ..chris
> 
> On Sun, Dec 7, 2008 at 2:45 PM, Gordon Heydon <gordon at heydon.com.au>
> wrote:
>> Hi
>>
>>
>>
>> On 08/12/2008, at 2:38 AM, Jakob Petsovits <jpetso at gmx.at> wrote:
>>
>>> On Sunday, 7. December 2008, Gordon Heydon wrote:
>>>>
>>>> I may take a look but it but I have a feeling I will need more than
>>>> what is available in the version control api
>>>>
>>>> Plus I want to make it pretty light weight so that adding this to a
>>>> site will have no impact
>>>
>>> Mmkay, no problem, just wanted to make sure that you consider the
>>> possibility
>>> before dismissing it :)
>>
>> I may actually use the version control api to extend the fuctionality and
>> not provide the base functionity.
>>>
>>> (I reserve the right to port good stuff to Version Control API, though.)
>>
>> No problem
>>
>> Gordon
>>
> 
> 

-- 
View this message in context: http://www.nabble.com/A-streamlined-way-to-develop-core-patches-tp20877884p21323239.html
Sent from the Drupal - Dev mailing list archive at Nabble.com.