From: Jody <jbruchon@nc.rr.com>
Cc: linux-8086@vger.kernel.org
Subject: Re: Updates
Date: Tue, 16 May 2006 22:42:43 -0400 [thread overview]
Message-ID: <446A8DA3.7030601@nc.rr.com> (raw)
In-Reply-To: <792c60620605161932u7993e66bh5c086df9277b06c1@mail.gmail.com>
Call me crazy. I like nice, unified snapshots as version control.
But if everyone gangs up on me wanting Subversion or something, we'll
see about setting it up.
By the way, when anyone does a "reply all" you need to delete my address
from the recipient list. I'm getting too many duplications of the same
message. Keep in mind that I get the same list I'm sending to.
Jody
Vikas Kumar wrote:
> Can we not use svn instead of CVS ?
> It is much easier to use.
> Vikas
>
> On 5/17/06, Jody <jbruchon@nc.rr.com> wrote:
>
>>
>>
>> Tom McCabe wrote:
>> > I have recently discovered, as of Tuesday evening,
>> > that Sourceforge's anonymous CVS for ELKS is up and
>> > running (Thanks, Jody!). It hasn't been edited in a
>>
>> I didn't do ANYTHING. Mike might have. I didn't understand why it was
>> BROKEN in the first place. I couldn't find any kind of documentation
>> that explained a way to bust the anonymous CVS. I used the developer's
>> CVS to get what I released at the beginning of the month and decided to
>> skip CVS altogether. I hate CVS anyway.
>>
>> Jody
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>
next prev parent reply other threads:[~2006-05-17 2:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 23:55 Updates Tom McCabe
2006-05-17 2:24 ` Updates Jody
2006-05-17 2:32 ` Updates Vikas Kumar
2006-05-17 2:42 ` Jody [this message]
2006-05-17 8:02 ` Updates Frank Gevaerts
2006-05-18 7:16 ` Updates Vojtěch Sázel
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=446A8DA3.7030601@nc.rr.com \
--to=jbruchon@nc.rr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox