[EventCalendar] Fatal Error with Big Calendar

Rick Boatright rboatright at gmail.com
Mon Oct 27 22:19:59 UTC 2008

Ahhh....   that makes sense.

And sadlly,  I'm the guy who deletes labels and re-creates them in Source
Safe because I wasn't REALLY REALLY ready.

DARCS (Which we use extensively)  doesn't actually support branches, (well,
it's more complex than that. - what isn't)  although it does (sort of)
support tags, but we don't use them.  It's a small team, and basically,
everyone is working in the same repository at the same time.

anyway,  I'll remember the convention.  But since this "tag"was less than 24
hours old,  I'm going to feel ok with that update this time.  :-)

Thanks  for the explanation.


On Mon, Oct 27, 2008 at 4:51 PM, Alex Tingle <alex at firetree.net> wrote:

>  Rick, I strongly recommend that you leave tags alone once you've made
>>> them.
>>> Make a new tag, rather than changing the one that's there.
> On 27 Oct 2008, at 21:26, Rick Boatright wrote:
>> uh  ok.
>> Sorry.
> No worries.
>  I'm sure there's a reason.   As I said, we use a _very_ different version
>> control system in my day to day life, and it simply doesn't _do_ tags and
>> branches and trunk.
>> I guess I ought to go read the nice - free, svn book.
> A 'tag' means a snapshot - it's a name for a frozen moment in the tree's
> history. Some revision control systems explicitly support the concept: CVS
> has 'tags', MS's Source Safe has 'labels'.
> Subversion doesn't explicitly support tags in code. Instead, it has a
> *convention* which is implemented purely at the human level: A directory
> called 'tags' is expected to contain copies of the tree that we don't intend
> to change.
> (Similarly, a directory called 'branches' is expected to contain copies of
> the tree that we DO intend to change.)
> There's always scope for bending these conventions. For example, if you
> remember something five minutes after you've tagged a release, it's probably
> OK to just dive in and change it. Once other people have started using your
> tag, then it's probably best to leave it and make another. If you flout the
> convention, you'll end up confusing people.
> -Alex
> _______________________________________________
> Blog: http://wpcal.firetree.net/
> EventCalendar at firetree.net mailing list
> Unsubscribe: http://penguin.firetree.net/eventcalendar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://penguin.firetree.net/pipermail/eventcalendar/attachments/20081027/cf5c600e/attachment.htm

More information about the EventCalendar mailing list