From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <archer@sourceware.org>
Subject: Archer git account inquiry
Date: Mon, 21 Feb 2011 13:27:00 -0000 [thread overview]
Message-ID: <00a901cbd1cb$01651880$042f4980$@muller@ics-cnrs.unistra.fr> (raw)
Hi all,
I have currently a very big patch that
solves several windows limitations:
- multi-inferior
- mutualization of some Ascii/Unicode variant
into a common/windows-hdep.[ch]
- start of support of 32-bit debugging within the 64-bit mingw64 debugger.
- support for non cygwin shells: msys shell /Windows COMSPEC variable
- translation of environment variables for Cygwin
But the total is a really big patch that I cannot
expect to get accepted as a whole,
thus I was wondering if I could get a account
with write access on the archer git to be able to more easily
separate out this huge patch into smaller
bits.
Do you know who I should
ask for this account?
I still don't really know git, but
I will try to read GitSvnCrashCourse
to get a first impression.
Pierre Muller
GDB pascal language maintainer
next reply other threads:[~2011-02-21 13:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 13:27 Pierre Muller [this message]
2011-02-21 14:22 ` [Archer] " Joel Brobecker
2011-02-21 14:34 ` Tom Tromey
2011-02-22 4:25 ` [Archer] " Joel Brobecker
2011-02-23 3:30 ` Joel Brobecker
2011-02-23 9:08 ` Pierre Muller
2011-02-23 9:19 ` [Archer] " Joel Brobecker
2011-02-23 20:21 ` Tom Tromey
2011-02-24 11:01 ` Jan Kratochvil
2011-02-24 11:11 ` Pierre Muller
2011-02-24 11:20 ` Pierre Muller
2011-02-24 11:29 ` Jan Kratochvil
2011-02-23 20:23 ` Tom Tromey
2011-02-24 3:22 ` [Archer] " Joel Brobecker
2011-02-21 14:31 ` Tom Tromey
2011-02-24 11:05 ` Pierre Muller
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='00a901cbd1cb$01651880$042f4980$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=archer@sourceware.org \
/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).