From: Christian Couder <firstname.lastname@example.org> To: jonathan chang <email@example.com> Cc: Thomas Gummerer <firstname.lastname@example.org>, Eric Sunshine <email@example.com>, git <firstname.lastname@example.org> Subject: Re: [GSoC][PATCH v2 1/5] t0000-basic: fix an indentation error Date: Fri, 15 Mar 2019 13:48:08 +0100 [thread overview] Message-ID: <CAP8UFD09QZd=6HyB5Om1PfV=67+CvfyQkcpLU0tukT48QccD0Q@mail.gmail.com> (raw) In-Reply-To: <CAOAu_YLTft7xmx4xvoM5Qqe0CHjqWrH+DUysHq0zfSEU8vodkg@mail.gmail.com> Hi, On Fri, Mar 15, 2019 at 2:55 AM jonathan chang <email@example.com> wrote: > > On Mon, Mar 11, 2019 at 1:59 AM Thomas Gummerer <firstname.lastname@example.org> wrote: > > > > On 03/10, Jonathan Chang wrote: > > > Also I found that there is no such function as test_char_count, > > > is it worthwile to add such function? Here are some stat: > > > > > > `git grep 'test_line_count' | wc -l` = 626 > > > `git grep 'wc -l' | wc -l` = 294 > > > `git grep 'wc -c' | wc -l` = 68 > > > > I do think it would be helpful to introduce that helper, especially if > > it is useful in this patch series. There seem to be enough other > > places where it can be useful to make it worth adding the helper. Yeah, it would be useful for Git, but it's not necessary of course for your microproject, which is already more than big enough. > > > This is a preparatory step prior to removing the pipes after git > > > commands, which discards git's exit code and may mask a crash. > > > > The commit message should also describe why we need this preparatory > > step. Maybe something like: > > > > To reduce the noise in when refactoring this pipeline in a > > subsequent commit fix the indentation. Or perhaps: Fix indentation of a line containing a pipeline to reduce the noise when refactoring the pipeline in a subsequent commit. > This has been wrong > > since the refactoring done in 1b5b2b641a ("t0000: modernise > > style", 2012-03-02), but carries no meaning. > > > > > Signed-off-by: Jonathan Chang <email@example.com> > > Since this patch series is now 5 patches, that commentary should go > > into a cover letter (see the --cover-letter option in format-patch), > > so the reviewers can read that first, and read the patches with that > > in mind, focusing on the patch only, and not additional commentary > > that applies to the whole series when reading the patch. > > I wasn't aware of this option. I tried to produce the format in others > cover letter using 'git diff' and options like '--stat', '--summary', with no > success. I consulted Documentation/SubmittingPatches, where I got the > idea of cover letter, but it doesn't mention the option '--cover-letter' and > the idea of cover letter is even confused with '--notes'. The issue is that there are different things that can be considered "cover letter". I agree that it's not very clear in Documentation/SubmittingPatches. There is the following which is related to --cover-letter: "Multiple related patches should be grouped into their own e-mail thread to help readers find all parts of the series. To that end, send them as replies to either an additional "cover letter" message (see below), the first patch, or the respective preceding patch." but it doesn't mention --cover-letter and it contains "(see below)" though I don't see what that refers to. > I just reread some of the GSoC related mails in the mailing list and > found one that introduced the usage of 'cover-letter', '--range-diff' and > '--interdiff'. As a newbie, I personally think it would be helpful to include > theses options along with others mentioned in SubmittingPatches. I agree that there is room for improvement in SubmittingPatches. Thanks, Christian.
next prev parent reply other threads:[~2019-03-15 12:48 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-09 15:45 [GSoC][PATCH] tests: avoid using pipes Jonathan Chang 2019-03-09 16:45 ` Thomas Gummerer 2019-03-10 8:07 ` [GSoC][PATCH v2 1/5] t0000-basic: fix an indentation error Jonathan Chang 2019-03-10 8:08 ` [GSoC][PATCH v2 2/5] t0000-basic: avoid using pipes Jonathan Chang 2019-03-10 8:09 ` [GSoC][PATCH v2 3/5] t0003-attributes: " Jonathan Chang 2019-03-10 8:10 ` [GSoC][PATCH v2 4/5] t0022-crlf-rename: " Jonathan Chang 2019-03-10 8:11 ` [GSoC][PATCH v2 5/5] t0000-basic: use test_line_count instead of wc -l Jonathan Chang 2019-03-10 9:50 ` Eric Sunshine 2019-03-11 16:10 ` ttjtftx 2019-03-10 10:03 ` [GSoC][PATCH v2 4/5] t0022-crlf-rename: avoid using pipes Eric Sunshine [not found] ` <CAOAu_YJKNjGd3mw7K17ySQJeF4XxC+V00FFEYA7o593riEGN1g@mail.gmail.com> 2019-03-11 15:54 ` Fwd: " ttjtftx 2019-03-10 10:13 ` [GSoC][PATCH v2 3/5] t0003-attributes: " Eric Sunshine 2019-03-15 1:56 ` jonathan chang 2019-03-10 17:59 ` [GSoC][PATCH v2 1/5] t0000-basic: fix an indentation error Thomas Gummerer 2019-03-15 1:55 ` jonathan chang 2019-03-15 12:48 ` Christian Couder [this message] 2019-03-10 6:05 ` [GSoC][PATCH] tests: avoid using pipes Christian Couder 2019-03-10 8:27 ` ttjtftx 2019-03-10 15:05 ` Christian Couder [not found] ` <CAOAu_YL8heWLSznRV8pjLkRZBOEth_7CSmftupx+4+SSx5yztw@mail.gmail.com> 2019-03-11 16:45 ` Fwd: " jonathan chang
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 List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAP8UFD09QZd=6HyB5Om1PfV=67+CvfyQkcpLU0tukT48QccD0Q@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [GSoC][PATCH v2 1/5] t0000-basic: fix an indentation error' \ /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
email@example.com list mirror (unofficial, one of many) This inbox may be cloned and mirrored by anyone: git clone --mirror https://public-inbox.org/git git clone --mirror http://ou63pmih66umazou.onion/git git clone --mirror http://czquwvybam4bgbro.onion/git git clone --mirror http://hjrcffqmbrq6wope.onion/git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V1 git git/ https://public-inbox.org/git \ firstname.lastname@example.org public-inbox-index git Example config snippet for mirrors. Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.version-control.git nntp://7fh6tueqddpjyxjmgtdiueylzoqt6pt7hec3pukyptlmohoowvhde4yd.onion/inbox.comp.version-control.git nntp://ie5yzdi7fg72h7s4sdcztq5evakq23rdt33mfyfcddc5u3ndnw24ogqd.onion/inbox.comp.version-control.git nntp://4uok3hntl7oi7b4uf4rtfwefqeexfzil2w6kgk2jn5z2f764irre7byd.onion/inbox.comp.version-control.git nntp://news.gmane.io/gmane.comp.version-control.git note: .onion URLs require Tor: https://www.torproject.org/ code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git AGPL code for this site: git clone https://public-inbox.org/public-inbox.git