Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: ieee--- via Gdb <gdb@sourceware.org>
To: gdb@sourceware.org
Subject: CONFLUENCE 2026 x GDB Community — Open-Source & Linux Bootcamp Collaboration
Date: Thu, 24 Sep 2026 07:26:31 -0700	[thread overview]
Message-ID: <CACkaYi_JnTTX3VtqsY2RE+f07D70f02fOhx4Ca2QLw17=SMSzw@mail.gmail.com> (raw)

Hi GDB,

I am reaching out on behalf of the IEEE Student Branch at Vivekananda
Institute of Professional Studies (VIPS-TC), Delhi. I serve as the
Chairperson of our IEEE student chapter.

We are organizing CONFLUENCE — IEEE DAY 2026 TechFest on 16–17 October
2026 in Delhi, India. The festival brings together 2,000+ verified
student developers, hackathon competitors, and researchers, with an
expected offline footfall of 10,000+ engineering students.

Our Open-Source & Linux Bootcamp brings together 1,500+ student
contributors and systems engineers. Partnering with GDB Community will
showcase your The GNU Project Debugger: allows you to see what is
going on inside another program while it executes (FSF) to upcoming
open-source maintainers.

Proposed collaboration:
- Assembly & Low-Level Debugging Workshop Partner + GNU GDB Badges
- Dedicated booth / developer workshop session for hands-on product adoption.
- Direct talent access to top 5% computer science undergraduates
across Delhi NCR.

I would love to set up a quick 10-minute discovery call or meet with
your team this week to explore this partnership and align on
deliverables.

Are you available for a brief chat this week?

Warm regards,

Aviral Bohra
Chairperson, IEEE Student Branch
Vivekananda Institute of Professional Studies – Technical Campus
(VIPS-TC), Delhi
Website: https://vips.edu | IEEE Delhi Section

                 reply	other threads:[~2026-09-24 14:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CACkaYi_JnTTX3VtqsY2RE+f07D70f02fOhx4Ca2QLw17=SMSzw@mail.gmail.com' \
    --to=gdb@sourceware.org \
    --cc=ieee@vips.edu \
    /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