From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: jason-swarelist@molenda.com
Cc: ac131313@cygnus.com, gdb@sources.redhat.com
Subject: Re: GDB 5.1.1 scheduled 00:00 24 Jan 2002 GMT
Date: Thu, 17 Jan 2002 23:31:00 -0000 [thread overview]
Message-ID: <1858-Fri18Jan2002092736+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <20020117131815.A27451@molenda.com> (message from Jason Molenda on Thu, 17 Jan 2002 13:18:15 -0800)
> Date: Thu, 17 Jan 2002 13:18:15 -0800
> From: Jason Molenda <jason-swarelist@molenda.com>
>
> By encoding the date in the branch tag, which
> people have to use often, you make them remember arbitrary information
> which doesn't disambiguate anything. I can check out a copy of
> the gcc 3.0 branch without looking at a single web page, without
> checking a single tag list -- any reasonable person can guess what
> it will look like. No reasonable person can guess what the gdb
> 5.1 branch name might be.
You mean, you don't have a small shell script for CVS command on the
branch (created when Andrew first announces the tag)? ;-)
next prev parent reply other threads:[~2002-01-18 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 13:07 Andrew Cagney
2002-01-17 13:12 ` Daniel Jacobowitz
2002-01-17 13:18 ` Jason Molenda
2002-01-17 13:59 ` Andrew Cagney
2002-01-17 23:31 ` Eli Zaretskii [this message]
2002-01-28 12:44 ` Andrew Cagney
2002-01-23 10:36 ` 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=1858-Fri18Jan2002092736+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=jason-swarelist@molenda.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