From: Jody <jody@jodybruchon.com>
To: linux-8086@vger.kernel.org
Subject: Re: ELKS Git repository up on SourceForge + patches applied
Date: Sun, 05 Feb 2012 14:22:15 -0500 [thread overview]
Message-ID: <4F2ED6E7.7020704@jodybruchon.com> (raw)
In-Reply-To: <CAMKR1ysAyZ7sDkmOBnDCcgs1rtLKQ_jnmRWJodAJg1Kp8cYebA@mail.gmail.com>
I just pushed the code to Git. I don't know much about CVS and I have
always personally hated it since I got on SourceForge 11 years ago. I
just wanted to get the code in an easily reachable place as quickly as I
could, so that's what I've done. Do we need the CVS history, moving forward?
On 2/5/2012 2:18 PM, Kirn Gill wrote:
>
> That's one better than I had planned. I was just going to push the
> changes to CVS and call it a day. Say, did you import all the CVS
> history into git or just a checkout of the latest sources + the patches?
>
>
next prev parent reply other threads:[~2012-02-05 19:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 19:12 ELKS Git repository up on SourceForge + patches applied Jody
[not found] ` <CAMKR1ysAyZ7sDkmOBnDCcgs1rtLKQ_jnmRWJodAJg1Kp8cYebA@mail.gmail.com>
2012-02-05 19:22 ` Jody [this message]
2012-02-05 19:32 ` Kirn Gill
2012-02-05 20:53 ` Mario Frasca
2012-02-05 21:09 ` Kirn Gill
2012-02-06 11:11 ` David Given
2012-02-05 21:14 ` Harley Laue
2012-02-05 23:17 ` Jody
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=4F2ED6E7.7020704@jodybruchon.com \
--to=jody@jodybruchon.com \
--cc=linux-8086@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 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.