This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Merge commits to master?



On 31/05/2016 11:35, Carlos O'Donell wrote:
> On 05/30/2016 06:34 PM, cvs-commit at gcc dot gnu.org wrote:
>> - Log -----------------------------------------------------------------
>> https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=7838d298d895f65247fb6b498db03a4336fc0506
>>
>> commit 7838d298d895f65247fb6b498db03a4336fc0506
>> Merge: ca7e8dd 600c13b
>> Author: Paul Pluzhnikov <ppluzhnikov@google.com>
>> Date:   Mon May 30 15:33:13 2016 -0700
>>
>>     Merge branch 'master' of ssh://sourceware.org/git/glibc
> 
> Paul,
> 
> Is there any reason you did a merge?
> 
> It is popular in Linux to do merges because of the highly distributed
> nature of the branches and workflow. I don't know that we will ever
> need that level of complexity in upstream glibc.
> 
> Should we be avoiding such merges and more simply commit fixes as
> commits which land on master?

I would prefer it, we do not have such load of commits and I think
a full commit message as we are aiming recently is better to document
the devel history.

> 
> Cheers,
> Carlos.
> 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]