From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Time to switch from CVS to GIT? [Re: [v8] multi-executable support]
Date: Wed, 14 Oct 2009 21:53:00 -0000 [thread overview]
Message-ID: <8ac60eac0910141453u2dd0f696pb4047c5f106aa5ce@mail.gmail.com> (raw)
On Wed, Oct 14, 2009 at 8:28 AM, Joel Brobecker <brobecker@adacore.com> wrote:
> Actually, not to worry after all. I modified my procedures to use
> the git repo instead, and it's very easy to go back, so cancel that
> personal request :).
>
> (after so many months of using git, I still cannot believe how much
> of a lifesaver it is - I keep discovering new ways to improve my work
> with it, and I simply have no time to get used to it!)
I don't recall this being discussed, sorry if it has been.
Should we switch to git as the primary repository?
Thanks,
--
Paul Pluzhnikov
next reply other threads:[~2009-10-14 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 21:53 Paul Pluzhnikov [this message]
2009-10-14 22:19 ` Joel Brobecker
2009-10-14 22:28 ` Paul Pluzhnikov
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=8ac60eac0910141453u2dd0f696pb4047c5f106aa5ce@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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