Hi,

2009/7/6 Stephen C. Gilardi <squee...@mac.com>:
>
> On Jul 6, 2009, at 3:13 PM, Tom Emerson wrote:
>
> Thanks Paul, for the quick response.
>
> On Mon, Jul 6, 2009 at 12:56 PM, Phil Hagelberg<p...@hagelb.org> wrote:
>
> That's right. Side note to folks with commit access: it would be a good
>
> idea to check in a note to the deprecated repositories telling people
>
> where to go for the latest versions.
>
> Or, better, do away with those obsolete repos entirely. But whatever.
>
> In the case of SourceForge, they have a strong preference for keeping old
> repos around. I think it's confusing, but I recall looking into it and
> finding that was their policy. I'm not sure whether or not Google Code has a
> similar preference. Some clear, local indication in each repository that
> marks it as "no longer maintained, see clojure.org for current info" would
> be a win of course.
>

I think there could be a way to make both parts happy : rather than
just adding the info that it is an old repo in some README file in the
root directory of the svn repo, committing also an svn delete command
on all the contents of trunk could help clarify this : by default,
users checking (or updating !) trunk would have an empty working copy
as a result (and also just the informative README file).
But tags would still be there, and also the entire repository history,
as a svn delete is just deleting files in the commited revision, not
deleting the history (one could retrieve a working copy by just
emitting svn up -r N-1  where N would be the "deletion" commit.

HTH,

-- 
Laurent

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to