git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: git <git@vger.kernel.org>
Subject: Tracking CVS
Date: Thu, 22 Jun 2006 08:41:16 -0400	[thread overview]
Message-ID: <9e4733910606220541y15d66fa6t33ab0c80ae05f764@mail.gmail.com> (raw)

I'm tracking cvs using this sequence.

cvs update
cg rm -a
cg commit
cg add -r .
cg commit

Is there a way to avoid the two commits? If you do the add with out
the intervening commit it just adds the files back.

-- 
Jon Smirl
jonsmirl@gmail.com

             reply	other threads:[~2006-06-22 12:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 12:41 Jon Smirl [this message]
2006-06-22 13:58 ` Tracking CVS Petr Baudis
2006-06-22 14:17   ` Jon Smirl
2006-07-19 12:38     ` Petr Baudis
2006-06-22 17:05   ` Junio C Hamano
2006-06-22 17:14     ` Jakub Narebski
2006-06-22 17:43       ` Junio C Hamano
2006-06-23  2:18   ` Jon Smirl
2006-06-23  2:24     ` Jon Smirl
2006-06-23  2:31     ` Petr Baudis
2006-06-23 18:14       ` Jon Smirl

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=9e4733910606220541y15d66fa6t33ab0c80ae05f764@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=git@vger.kernel.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).