From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa] doc/gdbint.texinfo: update commands for release tarball
Date: Fri, 10 Jan 2003 16:07:00 -0000 [thread overview]
Message-ID: <200301101607.h0AG7Oc23529@duracef.shout.net> (raw)
> I cut/paste these sequeces when doing a release (which is why they keep
> changing) so having just the new one there would break me doing a
> re-spin of the current branch :-)
Mmm, shouldn't you cut/paste out of doc/gdbint.texinfo in the
branch when you are spinning the branch?
> For the moment, I think clone it. (but add a cindex?)
I'm willing to clone it if I can't convince you to look in the right
place. :)
It just really frustrated me yesterday when you said 'there's a problem
in the snapshot tarball' and I could not make a snapshot tarball.
That's why I am keen on this.
Michael C
next reply other threads:[~2003-01-10 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 16:07 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-10 15:27 Michael Elizabeth Chastain
2003-01-10 15:58 ` Andrew Cagney
2003-01-10 5:29 Michael Elizabeth Chastain
2003-01-10 6:43 ` Andrew Cagney
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=200301101607.h0AG7Oc23529@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.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