public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Info <support@geckoboard.zendesk.com>
Cc: First <first@geckoboard.com>,
	 Geckoboard <support@geckoboard.com>,
	 Jim Karman <jim.karman@wildbluetech.com>,
	 Contact <contact@firstcom.fr>,
	 Conference <conference@elte-dh.hu>,
	 Karman <karman@wildbluetech.com>,
	 Jkarman <jkarman@wildbluetech.com>,
	 Info <info@westsideface.com>,  Info <info@livhealth.org>,
	 Intern <intern@wildbluetech.com>,  Office <office@glrec.com>,
	 Paul <paul@ncfitnessgear.com.au>,
	 J Lehouillier <j.lehouillier@dompteurs.com>,
	 Social <social@wildbluetech.com>,  Gai <gai@cohennorris.com>,
	 Info <info@gotthegoods.com>,  Info <info@wildbluetech.com>,
	 Gdb <gdb@sourceware.org>,  Info <info@cohennorris.com>
Subject: Your request is being processed
Date: Mon, 11 Sep 2023 02:52:46 +0000	[thread overview]
Message-ID: <WPKZGLJ4YNR_64fe80fe1cfae_3c46a012537ce_sprut@zendesk.com> (raw)
In-Reply-To: <VR3X7P9RJKZ_64fe80f55addb_4b46a09192649_sprut@zendesk.com>

[-- Attachment #1: Type: text/plain, Size: 296 bytes --]

 
## Please reply above this line ##

You are registered as a cc on this help desk request (Your request is being processed) and are thus receiving email notifications on all updates to the request.
Reply to this email to add a comment to the request.

 










[WPKZGL-J4YNR]

      reply	other threads:[~2023-09-11  2:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <VR3X7P9RJKZ@zendesk.com>
     [not found] ` <20230911115022.e02d8be181dca465c33d8361@do.ai>
2023-09-11  2:52   ` MrFluffyFriend™ | Customer Service
2023-09-11  2:52     ` Info [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=WPKZGLJ4YNR_64fe80fe1cfae_3c46a012537ce_sprut@zendesk.com \
    --to=support@geckoboard.zendesk.com \
    --cc=conference@elte-dh.hu \
    --cc=contact@firstcom.fr \
    --cc=first@geckoboard.com \
    --cc=gai@cohennorris.com \
    --cc=gdb@sourceware.org \
    --cc=info@cohennorris.com \
    --cc=info@gotthegoods.com \
    --cc=info@livhealth.org \
    --cc=info@westsideface.com \
    --cc=info@wildbluetech.com \
    --cc=intern@wildbluetech.com \
    --cc=j.lehouillier@dompteurs.com \
    --cc=jim.karman@wildbluetech.com \
    --cc=jkarman@wildbluetech.com \
    --cc=karman@wildbluetech.com \
    --cc=office@glrec.com \
    --cc=paul@ncfitnessgear.com.au \
    --cc=social@wildbluetech.com \
    --cc=support+id165432@geckoboard.zendesk.com \
    --cc=support@geckoboard.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.
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).