git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2 Outreachy] t7011: ensure no whitespace after redirect

From
Seyi Chamber <kuforiji98@gmail.com>
Date
Oct 21, 2024, 17:17 UTC
Message-ID
<CAGedMteMtaOvyE2gX59bMudEUmCZw7nOh=MuDRi=7CbYm-gBDQ@mail.gmail.com>
In-Reply-To
<ZxZDFyKxTn_D7c3o@pks.im>
On Mon, 21 Oct 2024 at 13:03, Patrick Steinhardt <ps@pks.im> wrote:
Show 22 quoted lines
>
> On Sat, Oct 19, 2024 at 07:54:30PM +0200, Kristoffer Haugsbakk wrote:
> > On Sat, Oct 19, 2024, at 18:34, Seyi Kuforiji wrote:
> > > This change updates the script to conform to the coding standards
> > > outlined in the Git project's documentation. According to the guidelines
> > > in Documentation/CodingGuidelines under "Redirection operators", there
> > > should be no whitespace after redirection operators.
> > >
> > > Signed-off-by: Seyi Kuforiji <kuforiji98@gmail.com>
> > > ---
> > >  t/t7011-skip-worktree-reading.sh | 22 +++++++++++-----------
> > >  1 file changed, 11 insertions(+), 11 deletions(-)
> >
> > I can confirm that there are no changes in this version to the patch
> > itself.  Which was expected since the change was good.
> >
> > The difference in this version is that the commit message has been
> > improved.  At least according to my taste.
>
> Agreed, this patch looks good to me, too. Thanks!
>
> Patrick
Yay!
Thank you for the feedback @Patrick Steinhardt @Kristoffer Haugsbakk
Regards
Seyi
Previous: Patrick SteinhardtNext: Taylor Blau
Message 4 of 9 in “t7011: ensure no whitespace after redirect”
  1. t7011: ensure no whitespace after redirectSeyi Kuforiji, Oct 19, 2024
  2. Kristoffer HaugsbakkOct 19, 2024
  3. Patrick SteinhardtOct 21, 2024
  4. Seyi ChamberOct 21, 2024
  5. Taylor BlauOct 21, 2024
  6. Seyi ChamberOct 22, 2024
  7. Patrick SteinhardtOct 23, 2024
  8. Seyi ChamberOct 23, 2024
  9. Patrick SteinhardtOct 23, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.