From: Andrew Shugg <andrew@neep.com.au>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Updated parisc-linux .cvsrc
Date: Mon, 12 Aug 2002 16:56:52 +0800 [thread overview]
Message-ID: <20020812165650.C897@neep.com.au> (raw)
In-Reply-To: <20020812102135.6bb1cff0.varenet@esiee.fr>; from varenet@esiee.fr on Mon, Aug 12, 2002 at 10:21:35AM +0200
Thibaut VARENE said:
> > In my experience it has been more common to fix the repository. =)
>
> Heh, sure, but this is not actually *possible*, so to speak: Matt
> pointed out that folders can't be removed from the repository, since
> they are mandatory to keep the 'Attic' in them.
>
> That allows anyone to grab an old version of the kernel, using cvs
> tags...
Oh I know, I'm aware of that, it was more of a joke. Some people use
CVS in a very carefree manner (shared bitbucket) and aren't really too
worried about breaking old versions. Why do they use CVS then? Good
question ... because it's there, I suppose.
Of course this is one of the main weaknesses in CVS, in case anyone out
there thinks it's the best thing since sliced bread: no revision control
on directories (folders/containers/collections/whatever). =)
Andrew.
--
Andrew Shugg <andrew@neep.com.au> http://www.neep.com.au/
"Just remember, Mr Fawlty, there's always someone worse off than yourself."
"Is there? Well I'd like to meet him. I could do with a good laugh."
prev parent reply other threads:[~2002-08-12 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-11 23:23 [parisc-linux] Updated parisc-linux .cvsrc Ryan Bradetich
2002-08-12 7:58 ` Andrew Shugg
2002-08-12 8:21 ` Thibaut VARENE
2002-08-12 8:56 ` Andrew Shugg [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=20020812165650.C897@neep.com.au \
--to=andrew@neep.com.au \
--cc=parisc-linux@lists.parisc-linux.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.