git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] cvs-migration documentation update
Date: Mon, 30 Jan 2006 22:40:37 -0500	[thread overview]
Message-ID: <20060131034036.GA17585@fieldses.org> (raw)
In-Reply-To: <7virs13x1i.fsf@assigned-by-dhcp.cox.net>

On Mon, Jan 30, 2006 at 07:18:17PM -0800, Junio C Hamano wrote:
> "J. Bruce Fields" <bfields@fieldses.org> writes:
> 
> > Here's some changes to the cvs-migration.txt.  As usual, in my attempt
> > to make things clearer someone may have found I've made them less so, or
> > I may have just gotten something wrong; so any review is welcomed.
> 
> Again, thanks for doing this.

Hey, it's fun.

> > -..., and the
> > -first step to recovery is admitting you have a problem. The fact that
> > -you are reading this file means that you may be well on that path
> > -already.
> > -
> > -The thing about CVS is that it absolutely sucks...
> > -
> > -One particular suckage of CVS is very hard to work around: CVS is...
> 
> Somehow I miss the above two paragraphs and a half ;-).

Hah.  Yes, understood.  But I figured a reader trying to migrate away
from CVS is more painfully aware of the above than anyone, so better to
just get out of their way and let them get on with it....

> But listing the differences as bullet points as you did makes
> things much clearer.  I like it.

OK!  Good.

> > +If some else has updated the repository more recently, `git push`, like
> 
> some else?

Whoops, thanks for noticing, should be "someone", obviously.

Let me know if you'd like a revised patch.--b.

      reply	other threads:[~2006-01-31  3:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-29  4:31 [PATCH] cvs-migration documentation update J. Bruce Fields
2006-01-31  3:18 ` Junio C Hamano
2006-01-31  3:40   ` J. Bruce Fields [this message]

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=20060131034036.GA17585@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).