On 01.12.2018 01:19, Nico Kadel-Garcia wrote:
> On Fri, Nov 30, 2018 at 8:20 AM Julian Foad <julianfoad_at_apache.org> wrote:
>> Nico Kadel-Garcia wrote:
>>> On Thu, Nov 29, 2018 at 10:31 PM 钱海远(Nathan) <qianhaiyuan_at_hikvision.com> wrote:
>>>> We want to develop a feature like git pull request .
>>>> [...]
>>> This seems infeasible. The working copy in which the merges would occur does not exist in the Subversion workflow.
>> Hello Nico! What do you mean? If Nathan is developing a Subversion pull request workflow, his software can create a WC when it needs one.
>>
>> Hello Nathan. I am having difficulty knowing what you really require. "Like git pull request" could mean lots of different things. It would help if you can describe exactly what you require.
>>
>> - Julian
> git pull requests perform a merge in the local repository.
There are no "git pull requests". There are GitHub pull requests, and
BitBucket pull requests, and Gerrit pull requests, and so on. It doesn't
really matter whether or not they're all implemented the same way.
> What you'd
> need to create for this is a local repository, not a working copy, and
> the working repository becomes part of a distributed source control
> system.
Nonsense. You're describing one _posslble_ way to implement a "code
review with automatic merge" workflow. What people tend to call "pull
requests" these days is a feature that's quite a bit older than git (or
bitkeeper before that) and worked just fine with centralised
repositories. Let's not confuse the forest and the trees.
-- Brane
Received on 2018-12-01 09:47:12 CET