This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB 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: Gerrit


On 2019-10-14 2:31 p.m., Eli Zaretskii wrote:
>> From: Tom Tromey <tom@tromey.com>
>> Cc: Simon Marchi <simon.marchi@polymtl.ca>,  gdb-patches@sourceware.org
>> Date: Mon, 14 Oct 2019 12:03:32 -0600
>>
>>>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
>>
>>>> The way I see it is that it's not really different than that person 
>>>> posting a patch with the same content on the mailing list.  It's the 
>>>> same content, just a different format.
>>
>> Eli> Not exactly: having the code in a branch of our repository (again,
>> Eli> assuming it can be regarded as "ours") means we are redistributing it,
>> Eli> whereas having it in an email does not.
>>
>> But the email is all archived, so I still don't see the distinction.
> 
> Anyone can send email to us, and we cannot be responsible for what
> they send.  By contrast, having it in our repository is tantamount to
> redistributing it, because repositories are nowadays treated as a
> means to distribute code (and some projects, like Gnulib, have no
> other means).

I'm not to sure how to continue this conversation.  What can we do to
settle this?

In the mean time, I think it's fairly low risk to carry on with the
project: we are not different from the thousands of public projects
using a git-based review system, and I have never heard of this
ever being an issue.  Of course, we need to be as vigilant as today
about what we merge in the master branch, since that will be what the
GNU project releases.

Simon


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