Subject: merge 44345 44346

From: zimoun <[email-masked]>
Date: Mon, 02 Nov 2020 12:47:15 +0100

merge 44345 44346
thanks

--
Hi Aniket,

Thank you for your patches.  You probably did:

  git send-email --to=[email-masked] 0001-gnu-Add-r-metafor.patch
  git send-email --to=[email-masked] 0002-gnu-Add-r-altmeta.patch

which opens 2 bugs reports, for instance #44345 and #44346.  Since the
second patch requires the first one, it is better to include them to the
same bug number.  The easiest to do so is:

  git format-patch --cover-letter
  # edit 0000-cover-letter.patch
  git send-email --to=[email-masked] 0000-cover-letter.patch
  # wait the bug number; check your INBOX
  git send-email --to=[email-masked] \
      0001-gnu-Add-r-metafor.patch \
      0002-gnu-Add-r-altmeta.patch

or something along these lines.  For example, the number 12345 could be
44345.

Well, it is a big deal; this email is sent to the server control to
merge the 2 bug numbers.  Hope that makes sense.

Thank you again for your contribution.

All the best,
simon