couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benoit Chesneau <>
Subject Re: can fauxton commit be tagged?
Date Mon, 17 Feb 2014 08:37:34 GMT
On Mon, Feb 17, 2014 at 9:20 AM, Garren Smith <> wrote:
> When are we actually moving over to the seperate repos and what are the git commands
to keep it in sync?

both merge repository are using splitted repository to my knowledge
(see my latest status abour rcouch).

I don't know any good solution in the mid term.

Either you patch the couchdb-fauxton repository using git format-patch
ad git am or maybe better we could introduce a git submodules in the
current couchdb master. So you would just have to update the
couchdb-fauxton repository. Maybe Paul will have a better idea.

I am just thinking it would be easier to synchronise it now, so the
work later will be minimal. But maybe that's not so important.

Looking at the diff with the rcouch merge repository that's already
mean that more than 50 patches will need to be added. Using the
couchdb-fauxton repository of course will solve that.

- benoit

> On 17 Feb 2014, at 10:11 AM, Benoit Chesneau <> 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 <> wrote:
>>> On Wed, Jan 29, 2014 at 10:32 PM, Sue <> 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 <>
>>>>>>> Seems awfully complicated to make fauxton erlang shaped when
>>>>>>> already have the simple static file handler.
>>>>>> depends if fauxton eed more in the future. but for now I agree. Not
>>>>>> though how the final build could be done for the release? sub-modules?
>>>>>> 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
>>>>> built in the appropriate piece of CouchDB and Fauxton would reflect the
>>>>> API's.
>>>>> So, the question remains; what needs to be done to move fauxton to the
>>>>> repo? IIUC these new repos aren't ready for consumption, yet. Is that

View raw message