From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Tom Tromey'" <tromey@redhat.com>
Cc: <gdb@sourceware.org>
Subject: RE: Question about TRUNK branch version name
Date: Thu, 31 Oct 2013 16:54:00 -0000 [thread overview]
Message-ID: <00a301ced659$d3ec5f80$7bc51e80$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <87a9hp2xnz.fsf@fleche.redhat.com>
> Pierre> Of course, changing -cvs to -git might
> Pierre> ender some scripts obsolete...
> Pierre> But I thought I would ask anyhow!
>
> While doing the conversion I purposely avoided trying to make any other
> process changes. My thinking was that this would both make the task
> simpler, and allow us to focus any discussions on the task at hand
> rather than get sidetracked into other disputes.
>
> Now that this is pretty much done I think it's fine if you want to make
> changes.
I didn't say it was important, but just wondered
if we should leave that untouched...
> I think there are a few things in gdb that don't really make
> sense in the post-git world.
Wooaah... you are going faster than light... :-)
git is already superseeded, so what's the name of the next level?
Pierre
prev parent reply other threads:[~2013-10-31 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 16:40 La Poste
2013-10-31 16:49 ` Tom Tromey
2013-10-31 16:54 ` Pierre Muller [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='00a301ced659$d3ec5f80$7bc51e80$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb@sourceware.org \
--cc=tromey@redhat.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