From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>, gdb@sources.redhat.com
Subject: Re: Changes to snapshot process ... ?
Date: Fri, 12 Oct 2001 12:53:00 -0000 [thread overview]
Message-ID: <3BC74A32.70803@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1011011100533.18580R-100000@is>
> On Thu, 11 Oct 2001, Andrew Cagney wrote:
>
>> > Suppose someone only wants the branch snapshots: can she easily find
>> > out which snapshot is which? If that's not easy, how about putting
>> > each type of snapshot into its own directory, to avoid confusion?
>
>>
>> Yes, agreed. You wouldn't have a suggestion for a directory name? One
>> would be gdb/snapshots/current/, as for the other. One thought would be
>> gdb/snapshots/stable/ however people may read more into that then they
>> should. I guess I should suggest gdb/snapshots/branch/ and see if
>> someone comes up with something better [:-)]
>
>
> Yes, gdb/snapshots/branch/ sounds good. Better yet, try something
> like gdb/snapshots/gdb-5.1-release-branch/.
I had some reservations over calling something 5.1 but I think I've
overcome that fear. So gdb/snapshots/5.1-branch (I think release and gdb
are redundant).
I'll tweek the scripts for this ready for tonight.
--
Next question is gdb/snapshots/gdb+dejagnu.tar.bz2.
Hmm, at present it is a hard link :-/ If it was a symlink would ftp
shadow systems be smart enough to copy the link and not the file?
Eliminate this and GDB can run nightly snaps of both the 5.1-branch and
current without a significant increase in shadow size.
Andrew
next prev parent reply other threads:[~2001-10-12 12:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 17:21 Andrew Cagney
2001-10-02 1:14 ` Eli Zaretskii
2001-10-02 8:58 ` Andrew Cagney
2001-10-02 10:07 ` Eli Zaretskii
2001-10-10 21:24 ` Andrew Cagney
2001-10-11 1:06 ` Eli Zaretskii
2001-10-12 12:53 ` Andrew Cagney [this message]
2001-10-12 13:22 ` Christopher Faylor
2001-10-13 10:25 ` Andrew Cagney
2001-10-13 10:53 ` Christopher Faylor
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=3BC74A32.70803@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@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