From: Jim Blandy <jimb@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] gdb.c++/pr-1023.exp: new test script
Date: Wed, 05 Feb 2003 07:24:00 -0000 [thread overview]
Message-ID: <vt2y94vrye0.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <200302050644.h156idD30649@duracef.shout.net>
Michael Elizabeth Chastain <mec@shout.net> writes:
> BTW, I have had bad experiences when I do a commit that encompasses
> more than the current directory. That's why I do one commit per
> directory. Do other people have this problem, or do I need to hit
> the CVS info page again?
I do it all the time. What was the problem?
next prev parent reply other threads:[~2003-02-05 7:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-05 6:44 Michael Elizabeth Chastain
2003-02-05 7:24 ` Jim Blandy [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-03 18:57 Michael Elizabeth Chastain
2003-02-03 18:05 Michael Elizabeth Chastain
2003-02-03 18:36 ` Daniel Jacobowitz
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=vt2y94vrye0.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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