couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Garren Smith <gar...@apache.org>
Subject Re: can fauxton commit be tagged?
Date Mon, 17 Feb 2014 08:20:44 GMT
When are we actually moving over to the seperate repos and what are the git commands to keep
it in sync?


On 17 Feb 2014, at 10:11 AM, Benoit Chesneau <bchesneau@gmail.com> wrote:

> the couchdb-fauxton repository has been created. Please keep it in sync :)
> 
> - benoit
> 
> On Sun, Feb 9, 2014 at 11:19 PM, Benoit Chesneau <bchesneau@gmail.com> wrote:
>> On Wed, Jan 29, 2014 at 10:32 PM, Sue <deathbearbrown@gmail.com> wrote:
>>> I'm fine with tagging my commits.
>> 
>> thanks. By tagging I meant adding smth like fauxton: in the commit line ;)
>> 
>> - benoit
>>> 
>>> 
>>> On Wed, Jan 29, 2014 at 4:31 PM, Simon Metson <simon@cloudant.com> wrote:
>>> 
>>>>>> Seems awfully complicated to make fauxton erlang shaped when we
>>>>>> already have the simple static file handler.
>>>>> 
>>>>> depends if fauxton eed more in the future. but for now I agree. Not sure
>>>>> though how the final build could be done for the release? sub-modules?
or
>>>>> just a curl fetch and that's all?
>>>> 
>>>> 
>>>> Assuming eed == need - I can't see how it would need more, it's a consumer
>>>> of the API not an API itself. If there was something it needed it would be
>>>> built in the appropriate piece of CouchDB and Fauxton would reflect the new
>>>> API's.
>>>> 
>>>> So, the question remains; what needs to be done to move fauxton to the new
>>>> repo? IIUC these new repos aren't ready for consumption, yet. Is that right?
>>>> 


Mime
View raw message