git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Shourya Shukla <shouryashukla.oo@gmail.com>
Cc: git@vger.kernel.org, kaartic.sivaraam@gmail.com,
	christian.couder@gmail.com
Subject: Re: [GSoC] Shourya's Blog
Date: Wed, 17 Jun 2020 13:35:17 -0700	[thread overview]
Message-ID: <xmqq4kr9toqi.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200616072108.GA10273@konoha> (Shourya Shukla's message of "Tue, 16 Jun 2020 12:51:08 +0530")

Shourya Shukla <shouryashukla.oo@gmail.com> writes:

> Hello all!
>
> This is the sixth installation of my weekly blog covering what I have
> learned in GSoC and other like stuff.
> https://shouryashukla.blogspot.com/2020/06/gsoc-week-55.html
>
> Feel free to comment!

This like looked unusual:

    var1=${var1:=$var2}

What's inside ${...} is sufficient to assing to var1 when it is not
uset or set to an empty string.  It is far more common to say

    : ${var1:=$var2}

with or without the colon in front of the equal sign (which tells
the construct to treat "set to empty" the same way as "unset").


  parent reply	other threads:[~2020-06-17 20:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16  7:21 [GSoC] Shourya's Blog Shourya Shukla
2020-06-17  8:38 ` Kaartic Sivaraam
2020-06-20  6:55   ` Shourya Shukla
2020-06-17 20:35 ` Junio C Hamano [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-08-24  7:50 Shourya Shukla
2020-08-05 17:46 Shourya Shukla
2020-08-14  7:14 ` Christian Couder
2020-07-28 10:11 Shourya Shukla
2020-07-14 22:10 Shourya Shukla
2020-07-05 18:38 Shourya Shukla
2020-06-28  9:39 Shourya Shukla
2020-06-23 18:14 Shourya Shukla
2020-05-27 16:20 Shourya Shukla
2020-05-28 13:15 ` Kaartic Sivaraam

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=xmqq4kr9toqi.fsf@gitster.c.googlers.com \
    --to=gitster@pobox.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kaartic.sivaraam@gmail.com \
    --cc=shouryashukla.oo@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).