zsh-workers
 help / color / mirror / code / Atom feed
From: dmeyer@jhereg.penguinpowered.com
To: zsh-workers@sunsite.auc.dk
Subject: sourceforge.net CVS tree ready for use
Date: Sun, 2 Apr 2000 10:06:17 -0400	[thread overview]
Message-ID: <20000402100617.A1617@jhereg.dmeyer.org> (raw)

In article <000201bf9c8b$a6655830$21c9ca95@mow.siemens.ru> you write:
> I successfully checked out and compiled Zsh from CVS. Congratulations!
> 
> Offtopic: anybody knows, how to find out, what branch was checked out?
> And the date? I mean, now, when reporting problems, we need some way to
> refer to "CVS branch xxx checked out/updated at yyy"

status -v <filename> will tell you if there is a sticky tag -
including sticky branch tag - or sticky date for a particular file.
It's pretty much up to you not to do anything foolish like check out
different files from different branches.

For the "checked out/updated at yyy" problem, I think the best
solution is for most people to use labeled versions, which shouldn't
be too onerous as long as folks are smart about creating new (and
cleaning up old and useless) labels.


-- 
David M. Meyer
dmeyer0@bellatlantic.net


             reply	other threads:[~2000-04-02 14:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-02 14:06 dmeyer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-28  0:28 move to sourceforge.net in progress Adam Spiers
2000-03-27 21:24 ` Peter Stephenson
2000-04-01 11:11   ` sourceforge.net CVS tree ready for use Adam Spiers
2000-04-01 20:51     ` Peter Stephenson
2000-04-02  0:44       ` Bart Schaefer
2000-04-02  0:45       ` Adam Spiers
2000-04-02  4:37         ` Bart Schaefer
2000-04-02  6:02           ` Geoff Wing
2000-04-02 22:02             ` Adam Spiers
2000-04-02 23:16               ` Bart Schaefer
2000-04-02 10:10     ` Andrej Borsenkow
2000-04-02 10:35       ` Geoff Wing
2000-04-02 23:29         ` Bart Schaefer
2000-04-03  8:50           ` Geoff Wing
2000-04-03 10:30     ` Oliver Kiddle
2000-04-03 13:06       ` Adam Spiers

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=20000402100617.A1617@jhereg.dmeyer.org \
    --to=dmeyer@jhereg.penguinpowered.com \
    --cc=dmeyer0@bellatlantic.net \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).