On Nov 17, 2013, at 10:57 AM, Marty Sweet <msweet....@gmail.com> wrote:

> Jumped the gun! Is this the correct one:
> https://github.com/apache/cloudstack-docs ?
> 
> 4.2 or master?
> 

yes, even though I tend to use the apache main:

https://git-wip-us.apache.org/repos/asf?p=cloudstack-docs.git

updates to both 4.2 and master.


> Marty
> 
> 
> On Sun, Nov 17, 2013 at 3:56 PM, Marty Sweet <msweet....@gmail.com> wrote:
> 
>> Hi Sebastien,
>> 
>> Thanks for looking at this, what repo should I be committing to/pulling
>> from? I can't find anything solid on confluence.
>> 
>> Marty
>> 
>> 
>> On Fri, Nov 8, 2013 at 9:15 AM, Sebastien Goasguen <run...@gmail.com>wrote:
>> 
>>> 
>>> On Oct 27, 2013, at 7:02 AM, Marty Sweet <msweet....@gmail.com> wrote:
>>> 
>>>> Hi,
>>>> 
>>>> Is there any update on this?
>>>> My commit
>>>> 
>>> https://github.com/apache/cloudstack/commit/f5e7f46dadda741f10e5b674d0578ade9ba719d7
>>>> made
>>>> it into the 4.2.0 docs but
>>>> 
>>> https://github.com/apache/cloudstack/commit/922ef76224d4a8534f67f47b97cf664e5c65ecba
>>>> hasn't,
>>>> I have gone to use this several times just to remember it's not there :)
>>> 
>>> Marty, I commented on your patch:
>>> https://reviews.apache.org/r/13745/
>>> 
>>> Seems to me your patch was lost somehow in the move to the new repo.
>>> 
>>> Can you also make sure that you have your author info in there, otherwise
>>> we loose the authorship info.
>>> Just use git config to set your name and email in your patch.
>>> 
>>> thanks,
>>> 
>>> -sebastien
>>> 
>>>> 
>>>> Thanks,
>>>> Marty
>>>> 
>>>> 
>>>> On Thu, Oct 10, 2013 at 10:05 AM, Daan Hoogland <
>>> daan.hoogl...@gmail.com>wrote:
>>>> 
>>>>> Marty,
>>>>> 
>>>>> As I understand the master branch for docs will be filled as work on
>>>>> it starts. the ones in the 4.2 branch are the current ones.
>>>>> 
>>>>> btw commits get hidden, rarely lost :p
>>>>> 
>>>>> regards,
>>>>> 
>>>>> On Thu, Oct 10, 2013 at 8:29 AM, Marty Sweet <msweet....@gmail.com>
>>> wrote:
>>>>>> Where will the docs commited to the master become available? This
>>>>> probably
>>>>>> isn't the only case where commits have been lost?
>>>>>> 
>>>>>> https://reviews.apache.org/r/13745/
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On Thu, Oct 10, 2013 at 1:17 AM, Radhika Puthiyetath <
>>>>>> radhika.puthiyet...@citrix.com> wrote:
>>>>>> 
>>>>>>> 4.2 docs are from 4.2 branch.
>>>>>>> 
>>>>>>> -----Original Message-----
>>>>>>> From: Marty Sweet [mailto:msweet....@gmail.com]
>>>>>>> Sent: Thursday, October 10, 2013 3:27 AM
>>>>>>> To: dev@cloudstack.apache.org
>>>>>>> Subject: Re: [DOC] 4.2.0 Templates
>>>>>>> 
>>>>>>> Hi Daan,
>>>>>>> 
>>>>>>> Yeah the doc directory in the repo commited to master, where is the
>>>>>>> current
>>>>>>> 
>>>>> 
>>> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/Admin_Guide/working-with-templates.html
>>>>>>> being
>>>>>>> built from?
>>>>>>> 
>>>>>>> Marty
>>>>>>> 
>>>>>>> 
>>>>>>> On Wed, Oct 9, 2013 at 8:55 PM, Daan Hoogland <
>>> daan.hoogl...@gmail.com
>>>>>>>> wrote:
>>>>>>> 
>>>>>>>> Marty,
>>>>>>>> 
>>>>>>>> I am not sure what you mean. Do you mean the doc dir in the repo? I
>>>>>>>> think you need to look in
>>>>>>>> https://git-wip-us.apache.org/repos/asf/cloudstack-docs.git for the
>>>>>>>> 4.2 docs.
>>>>>>>> 
>>>>>>>> regards,
>>>>>>>> Daan
>>>>>>>> 
>>>>>>>> On Sun, Oct 6, 2013 at 10:51 PM, Marty Sweet <msweet....@gmail.com>
>>>>>>> wrote:
>>>>>>>>> Hi guys,
>>>>>>>>> 
>>>>>>>>> I created a document for creating Linux documentation for the 4.2.0
>>>>>>>>> release. Checking the documentation it seems that it is not there?
>>>>>>>>> Is
>>>>>>>> there
>>>>>>>>> any reason for this?
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>> http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.2.0/html/A
>>>>>>>> dmin_Guide/working-with-templates.html
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>> https://github.com/apache/cloudstack/commit/922ef76224d4a8534f67f47b97
>>>>>>>> cf664e5c65ecba
>>>>>>>>> https://issues.apache.org/jira/browse/CLOUDSTACK-4329
>>>>>>>>> 
>>>>>>>>> Thanks,
>>>>>>>>> Marty
>>>>>>>> 
>>>>>>> 
>>>>> 
>>> 
>>> 
>> 

Reply via email to