From: daniel@bigwalter.net (Daniel Jensen)
To: info-gnus-english@gnu.org
Subject: Re: A question about cvs
Date: Thu, 02 Aug 2007 15:21:01 +0200 [thread overview]
Message-ID: <87k5se3wea.fsf@orme.bigwalter.net> (raw)
In-Reply-To: <liyps26f67y.fsf@pegase.inria.fr>
Jean-Marc Lasgouttes <Jean-Marc.Lasgouttes@inria.fr> writes:
> daniel@bigwalter.net (Daniel Jensen) writes:
>
>> For CVS, why not go with HEAD?
>
> Don't know. I guess I wanted to stay on the 'slightly adventurous'
> side of things. Is HEAD stable enough in practice?
It depends -- YMMV, of course. I used to update sporadically from CVS
and I seldom experienced problems. Now I wait for No Gnus releases (that
is once a year or so), because there is no real reason for me to follow
CVS. I guess you could call this "slightly adventurous"?
next prev parent reply other threads:[~2007-08-02 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 12:59 Jean-Marc Lasgouttes
2007-08-02 12:39 ` Daniel Jensen
2007-08-02 12:53 ` Jean-Marc Lasgouttes
2007-08-02 13:21 ` Daniel Jensen [this message]
2007-08-02 13:34 ` Jean-Marc Lasgouttes
2007-08-02 19:27 ` Reiner Steib
2007-08-02 15:57 ` Adam Sjøgren
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=87k5se3wea.fsf@orme.bigwalter.net \
--to=daniel@bigwalter.net \
--cc=info-gnus-english@gnu.org \
/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;
as well as URLs for NNTP newsgroup(s).