Gnus development mailing list
 help / color / mirror / Atom feed
From: Steve Youngs <youngs@xemacs.org>
Subject: Re: patch: nnmaildir expiry improvements
Date: Fri, 04 Jan 2002 06:44:56 +1000	[thread overview]
Message-ID: <microsoft-free.x4lmfftb93.fsf@slackware.mynet.pc> (raw)
In-Reply-To: <m31yh7ic8g.fsf@multivac.cwru.edu> (prj@po.cwru.edu's message of "Thu, 03 Jan 2002 12:18:49 -0500")

|--==> "PJ" == Paul Jarc <prj@po.cwru.edu> writes:

  PJ> Ok, I have write access now.  So when I do "cvs commit lisp/nnmaildir.el",
  PJ> I get a buffer to edit.  Is this where I add my ChangeLog entry (along
  PJ> with a timestamp line)?

I'd suggest that it you're not familiar with CVS you set up a "test"
project on your local system.  That way you'll be able to see what
happens from both the client and server side of CVS.

Once you get to know the basic CVS commands have a look at the elisp
package, "PCL-CVS".  It makes CVS'ing from within (X)Emacs so much
easier.  It's what I use for all the projects that I have commit
privileges for (I think Lars uses it too).

Further reading:

        M-x manual-entry RET cvs RET
        M-x manual-entry RET cvs(5) RET
        M-x manual-entry RET co RET
        M-x manual-entry RET ci RET
        M-x manual-entry RET rcs RET
        C-h C-i cvs RET
        C-h C-i pcl-cvs RET

Have fun with it!  And don't worry, there's not too much that you can
break that can't be easily fixed. :-P


-- 
|---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---|
|            XEmacs - It's not just an editor.             |
|                    It's a way of life.                   |
|------------------------------------<youngs@xemacs.org>---|



  parent reply	other threads:[~2002-01-03 20:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-02 22:44 Paul Jarc
2002-01-03 17:18 ` Paul Jarc
2002-01-03 17:31   ` Lars Magne Ingebrigtsen
2002-01-03 20:44   ` Steve Youngs [this message]
2002-01-03 18:14 ` Paul Jarc
2002-01-03 18:33   ` Lars Magne Ingebrigtsen

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=microsoft-free.x4lmfftb93.fsf@slackware.mynet.pc \
    --to=youngs@xemacs.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).