can fauxton commit be tagged?

[Benoit Chesneau <bc...@gmail.com>]

There are a lot of fauxton commits landing in master. Which is fine I guess
but that makes it hard to check other commits. Can you eventually tag them
 with "fauxton:" or whatever saying fauxton. It will be a lot easier to
filter when looking for other patches.

Thanks!

- benoit

Re: can fauxton commit be tagged?

[Paul Davis <pa...@gmail.com>]

Fauxton is actually fairly simple to split out with subtree. I
wouldn't worry about maintaining things in sync just yet.

On Mon, Feb 17, 2014 at 2:37 AM, Benoit Chesneau <bc...@gmail.com> wrote:
> On Mon, Feb 17, 2014 at 9:20 AM, Garren Smith <ga...@apache.org> 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 <bc...@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 <bc...@gmail.com> wrote:
>>>> On Wed, Jan 29, 2014 at 10:32 PM, Sue <de...@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 <si...@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?
>>>>>>
>>

Re: can fauxton commit be tagged?

[Benoit Chesneau <bc...@gmail.com>]

On Mon, Feb 17, 2014 at 9:20 AM, Garren Smith <ga...@apache.org> 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 <bc...@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 <bc...@gmail.com> wrote:
>>> On Wed, Jan 29, 2014 at 10:32 PM, Sue <de...@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 <si...@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?
>>>>>
>

Re: can fauxton commit be tagged?

[Garren Smith <ga...@apache.org>]

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 <bc...@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 <bc...@gmail.com> wrote:
>> On Wed, Jan 29, 2014 at 10:32 PM, Sue <de...@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 <si...@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?
>>>> 

Re: can fauxton commit be tagged?

[Benoit Chesneau <bc...@gmail.com>]

the couchdb-fauxton repository has been created. Please keep it in sync :)

- benoit

On Sun, Feb 9, 2014 at 11:19 PM, Benoit Chesneau <bc...@gmail.com> wrote:
> On Wed, Jan 29, 2014 at 10:32 PM, Sue <de...@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 <si...@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?
>>>

Re: can fauxton commit be tagged?

[Benoit Chesneau <bc...@gmail.com>]

On Wed, Jan 29, 2014 at 10:32 PM, Sue <de...@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 <si...@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?
>>

Re: can fauxton commit be tagged?

[Sue <de...@gmail.com>]

I'm fine with tagging my commits.


On Wed, Jan 29, 2014 at 4:31 PM, Simon Metson <si...@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?
>

Re: can fauxton commit be tagged?

[Benoit Chesneau <bc...@gmail.com>]

On Wed, Jan 29, 2014 at 10:31 PM, Simon Metson <si...@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?


Forgot to answer. Since then, things moved faster and Paul has
splitted all repos and created the multirepo branch of bigcouch. I
will do the same for rcouch in the morning.

imo putting fauxton in couchdb-fauxton with a simple Makefile would be
enough if you don't need any specific handler. The repo already exists
(couchdb-fauxton). Would be cool if you could add the current code to
it :)

- benoit

Re: can fauxton commit be tagged?

[Simon Metson <si...@cloudant.com>]

> > 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?

Re: can fauxton commit be tagged?

[Benoit Chesneau <bc...@gmail.com>]

On Wed, Jan 29, 2014 at 8:45 PM, Paul Davis <pa...@gmail.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?


>
> On Wed, Jan 29, 2014 at 4:58 AM, Benoit Chesneau <bc...@gmail.com>
> wrote:
> > On Wed, Jan 29, 2014 at 11:25 AM, Simon Metson <si...@cloudant.com>
> wrote:
> >
> >> What's needed to complete that (if only for fauxton)? Is it just a case
> of
> >> importing code to the new repo and changing origins, or is there more
> (e.g.
> >> Build scripts)?
> >>
> >
> >
> > I was thinking to this. Maybe this can be done in a way fauxton would be
> > added as an Erlang application
> >
> > src/fauxton.erl
> > priv/,,,
> > js_src/
> >
> >
> > fauxton.erl could be the HTTP handler needed to expose it to the HTTP
> api.
> >
> > ?
> >
> > - benoit
>

Re: can fauxton commit be tagged?

[Paul Davis <pa...@gmail.com>]

Seems awfully complicated to make fauxton erlang shaped when we
already have the simple static file handler.

On Wed, Jan 29, 2014 at 4:58 AM, Benoit Chesneau <bc...@gmail.com> wrote:
> On Wed, Jan 29, 2014 at 11:25 AM, Simon Metson <si...@cloudant.com> wrote:
>
>> What's needed to complete that (if only for fauxton)? Is it just a case of
>> importing code to the new repo and changing origins, or is there more (e.g.
>> Build scripts)?
>>
>
>
> I was thinking to this. Maybe this can be done in a way fauxton would be
> added as an Erlang application
>
> src/fauxton.erl
> priv/,,,
> js_src/
>
>
> fauxton.erl could be the HTTP handler needed to expose it to the HTTP api.
>
> ?
>
> - benoit

Re: can fauxton commit be tagged?

[Benoit Chesneau <bc...@gmail.com>]

On Wed, Jan 29, 2014 at 11:25 AM, Simon Metson <si...@cloudant.com> wrote:

> What's needed to complete that (if only for fauxton)? Is it just a case of
> importing code to the new repo and changing origins, or is there more (e.g.
> Build scripts)?
>


I was thinking to this. Maybe this can be done in a way fauxton would be
added as an Erlang application

src/fauxton.erl
priv/,,,
js_src/


fauxton.erl could be the HTTP handler needed to expose it to the HTTP api.

?

- benoit

Re: can fauxton commit be tagged?

[Simon Metson <si...@cloudant.com>]

What's needed to complete that (if only for fauxton)? Is it just a case of importing code to the new repo and changing origins, or is there more (e.g. Build scripts)? 


On Wednesday, 29 January 2014 at 10:03, Benoit Chesneau wrote:

> On Wed, Jan 29, 2014 at 11:00 AM, Alexander Shorin <kx...@gmail.com> wrote:
> 
> > While we're going to multirepos does this really need?
> > I think it's good reminder to migrate project structure ASAP to reduce
> > overall annoying level (;
> > 
> 
> 
> agree, but until we go to that ...
> 
> - benoit
> 
> > --
> > ,,,^..^,,,
> > 
> > 
> > On Wed, Jan 29, 2014 at 1:55 PM, Benoit Chesneau <bc...@gmail.com>
> > wrote:
> > > There are a lot of fauxton commits landing in master. Which is fine I
> > 
> > guess
> > > but that makes it hard to check other commits. Can you eventually tag
> > 
> > them
> > > with "fauxton:" or whatever saying fauxton. It will be a lot easier to
> > > filter when looking for other patches.
> > > 
> > > Thanks!
> > > 
> > > - benoit 

Re: can fauxton commit be tagged?

[Benoit Chesneau <bc...@gmail.com>]

On Wed, Jan 29, 2014 at 11:00 AM, Alexander Shorin <kx...@gmail.com> wrote:

> While we're going to multirepos does this really need?
> I think it's good reminder to migrate project structure ASAP to reduce
> overall annoying level (;
>

agree, but until we go to that ...

- benoit

> --
> ,,,^..^,,,
>
>
> On Wed, Jan 29, 2014 at 1:55 PM, Benoit Chesneau <bc...@gmail.com>
> wrote:
> > There are a lot of fauxton commits landing in master. Which is fine I
> guess
> > but that makes it hard to check other commits. Can you eventually tag
> them
> >  with "fauxton:" or whatever saying fauxton. It will be a lot easier to
> > filter when looking for other patches.
> >
> > Thanks!
> >
> > - benoit
>

Re: can fauxton commit be tagged?

[Alexander Shorin <kx...@gmail.com>]

While we're going to multirepos does this really need?
I think it's good reminder to migrate project structure ASAP to reduce
overall annoying level (;
--
,,,^..^,,,


On Wed, Jan 29, 2014 at 1:55 PM, Benoit Chesneau <bc...@gmail.com> wrote:
> There are a lot of fauxton commits landing in master. Which is fine I guess
> but that makes it hard to check other commits. Can you eventually tag them
>  with "fauxton:" or whatever saying fauxton. It will be a lot easier to
> filter when looking for other patches.
>
> Thanks!
>
> - benoit

Re: can fauxton commit be tagged?

[Benoit Chesneau <bc...@gmail.com>]

On Wed, Jan 29, 2014 at 10:55 AM, Benoit Chesneau <bc...@gmail.com>wrote:

> There are a lot of fauxton commits landing in master. Which is fine I
> guess but that makes it hard to check other commits. Can you eventually tag
> them  with "fauxton:" or whatever saying fauxton. It will be a lot easier
> to filter when looking for other patches.
>
> Thanks!
>
> - benoit
>
>
> Just an example, the list of 60 patches I have to apply since I started
the rcouch merge branch:

https://www.friendpaste.com/7voDrcGTN0IY5rSfDCrQE

Most are related to fauxton :)

- benoit