From: Simon Marchi <simon.marchi@polymtl.ca>
To: Eli Zaretskii <eliz@gnu.org>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Gerrit
Date: Tue, 15 Oct 2019 01:33:00 -0000 [thread overview]
Message-ID: <ba1a12ad-63f2-add0-fd4c-e04976a662fd@polymtl.ca> (raw)
In-Reply-To: <83d0ezi3fr.fsf@gnu.org>
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
next prev parent reply other threads:[~2019-10-15 1:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 4:54 [PATCH] gdb: remove unused includes from dwarf2read.c Simon Marchi
2019-10-14 14:22 ` Simon Marchi
2019-10-14 14:39 ` Eli Zaretskii
2019-10-14 15:18 ` Simon Marchi
2019-10-14 17:12 ` Gerrit (was: [PATCH] gdb: remove unused includes from dwarf2read.c) Eli Zaretskii
2019-10-14 17:31 ` Gerrit Simon Marchi
2019-10-14 17:56 ` Gerrit Eli Zaretskii
2019-10-14 18:03 ` Gerrit Tom Tromey
2019-10-14 18:32 ` Gerrit Eli Zaretskii
2019-10-15 1:33 ` Simon Marchi [this message]
2019-10-15 8:51 ` Gerrit Eli Zaretskii
2019-10-15 15:57 ` Gerrit Sergio Durigan Junior
2019-10-15 16:33 ` Gerrit Eli Zaretskii
2019-10-15 17:09 ` Gerrit Sergio Durigan Junior
2019-10-15 17:31 ` Gerrit Eli Zaretskii
2019-10-15 17:49 ` Gerrit Sergio Durigan Junior
2019-10-14 23:51 ` Gerrit Simon Marchi
2019-10-14 18:02 ` [PATCH] gdb: remove unused includes from dwarf2read.c Luis Machado
2019-10-14 20:58 ` Simon Marchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ba1a12ad-63f2-add0-fd4c-e04976a662fd@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox