From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 435B2C433E0 for ; Sat, 23 Jan 2021 08:21:08 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E5511233EF for ; Sat, 23 Jan 2021 08:21:07 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726309AbhAWITJ (ORCPT ); Sat, 23 Jan 2021 03:19:09 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56522 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725932AbhAWITI (ORCPT ); Sat, 23 Jan 2021 03:19:08 -0500 Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 078E4C06174A for ; Sat, 23 Jan 2021 00:18:27 -0800 (PST) Received: by mail-ot1-x32b.google.com with SMTP id f6so7543100ots.9 for ; Sat, 23 Jan 2021 00:18:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=L14v/AJfDjtFDATx8hiY6Ej4GEt+cvciZKzWS8kqTSw=; b=iBj0o2kKNZhlCNixha9o176gIFUb2Ikg68zHifXPlrqhRYlJSwdLuDo0djLLZZAsda Yag0SeMuSd7gv9fecE7Kaetk4pJHRNbUJCRzO1R9rYWfvFuHova/LYx7vfBsbqhldXrw xEEnuyaqkrk7Vpc3dIFvHSduUosOU7MfHchtOb6OP2fKzXbkd1zlIklBZ+3vPJ2td5KF IzGEGD5iwPcdZtJ3+wrmQJoR98JB1/OYMzgIDqeQJjYH5WXq0uD0Ozm2KCg+kiylCNJb ITxveKrvUNNK16mwcGpcmeEYLOGV/jWuZqvOxheLdb8hFLGrcOiFpLv1S8SzS5UyYHoX j/Rw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=L14v/AJfDjtFDATx8hiY6Ej4GEt+cvciZKzWS8kqTSw=; b=tTix4PRLkPMNMQx4/TY87aULjoEtErxX8uwQcgWdtbXMoTHxeitbKxEdI2UzQSEKmA X7vAxDmaqvQZatqjep+eLOuMQdHGkJtLJ9YeXx+u4AuC2dbStCB+IzShgz5N4w9b5sZ3 O36tKU3KuO1NVGFjnwTKNKUwKcqQrUADv5rFkmMYLOvPIktjqNlqJjiTWMpPXhYq1aXl sVEWW35I5osw3++X+JNMG1JP48fwCo2VZ+sJB/rWsdLMZ2/YZUDcBHwUCaW9vsKDA2Xr HsY0b/5ElfmZTEPiM2CNsYxzaS6iNePEPPnDxBXfE0jyP9ucQX1v1Sa0bKYTl92JxDGP lGJQ== X-Gm-Message-State: AOAM530lXhOKrIRUHggmFjgKhxZswx8m6naTIo4q82b2fI8EztlKrvo2 4x6StmzWSdCQQaeuamDzks8syPl2pZn3CUjskOk= X-Google-Smtp-Source: ABdhPJyLYL0l6HY0rAgVwWL/FYALzildLc3hfYLMLOx0Gmh08BgIfBI0QRPO06coOflmXTcU2hnQSsDFcf9SLNOUESk= X-Received: by 2002:a9d:4812:: with SMTP id c18mr5769456otf.160.1611389907278; Sat, 23 Jan 2021 00:18:27 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?B?6IOh5ZOy5a6B?= Date: Sat, 23 Jan 2021 16:20:02 +0800 Message-ID: Subject: Re: [PATCH v5 3/3] ls-files.c: add --deduplicate option To: Johannes Schindelin Cc: ZheNing Hu via GitGitGadget , Git List , Eric Sunshine , Junio C Hamano Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Hi Johannes Schindelin, Thanks for prompt me how to choose, maybe I was a little confused about the git workflow before, "zh/ls-files-deduplicate" this kind of branch I don't need to operate,right? Well, then I will modify my code on the original branch. Johannes Schindelin =E4=BA=8E2021=E5=B9=B41=E6= =9C=8823=E6=97=A5=E5=91=A8=E5=85=AD =E4=B8=8A=E5=8D=8812:04=E5=86=99=E9=81= =93=EF=BC=9A > > Hi =E8=83=A1=E5=93=B2=E5=AE=81, > > On Fri, 22 Jan 2021, =E8=83=A1=E5=93=B2=E5=AE=81 wrote: > > > And should I still use gitgitgadget PR on my origin branch "dedup"or > > send patch on branch "zh/ls-files-deduplicate"? > > The way GitGitGadget is designed asks for contributors to adjust their > patch(es) via interactive rebase, implementing the suggestions and > addressing the concerns while doing so, then force-pushing, optionally > amending the first PR comment (i.e. the description) with a list of > those changes, and then submitting a new iteration via `/submit`. > > Ciao, > Johannes