All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryn M. Reeves" <bmr@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Justin Lee <justinlee5455@gmail.com>
Subject: Re: [linux-lvm] Failed to login LVM CVS
Date: Wed, 25 Sep 2013 11:26:27 +0100	[thread overview]
Message-ID: <5242BA53.7030905@redhat.com> (raw)
In-Reply-To: <CAHuLeSnj8SrvF=Q5jq2WE5S1CjJwisX+3oTb5760uR94rkVfnw@mail.gmail.com>

On 09/25/2013 11:11 AM, Justin Lee wrote:
> I wanted to get the source code of LVM 2.02.86(2) (2011-07-08) and I
> saw the instructions on web page
> http://www.tldp.org/HOWTO/html_single/LVM-HOWTO/#checkoutsource to
> check out the source from CVS. So I gave it a try and I got an error
> like this:

The primary version control system was moved from CVS to git in June of
last year:

https://sourceware.org/lvm2/

You can clone the repo with the following command:

  $ git clone git://git.fedorahosted.org/git/lvm2.git
  [...]

Then checkout the v2_02_86 tag:

  $ git checkout v2_02_86
  Note: checking out 'v2_02_86'.

  You are in 'detached HEAD' state. You can look around, make
  experimental changes and commit them, and you can discard any commits
  you make in this state without impacting any branches by performing
  another checkout.

  If you want to create a new branch to retain commits you create, you
  may do so (now or later) by using -b with the checkout command again.
  Example:

  git checkout -b new_branch_name

  HEAD is now at 4c67e55... remove unnecessary lvconvert.h

Following this your lvm2 directory will contain the sources as they were
at the time that tag was created.

Regards,
Bryn.

      reply	other threads:[~2013-09-25 10:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-25 10:11 [linux-lvm] Failed to login LVM CVS Justin Lee
2013-09-25 10:26 ` Bryn M. Reeves [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=5242BA53.7030905@redhat.com \
    --to=bmr@redhat.com \
    --cc=justinlee5455@gmail.com \
    --cc=linux-lvm@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.