Mark Wedel wrote:
> If a distributed model is used, this is how I would see local branches in
> use:
>
Agreed on the points you mentioned, just one comment.
> I note that in all of these cases, this is basically functionality that CVS
> doesn't really support well. I'd have to double chec
If a distributed model is used, this is how I would see local branches in use:
- Mirrors of the official repository - could be for speed reasons (one in
europe, one in asia, or just in general to cover outages if the official
repository is down).
- For developers to make their changes easily
Nicolas Weeger (Laposte) wrote:
> I won't comment on the priority, just other things :)
>
>> Better NPC logic 1.x?1
>
> Can be scripted. I'm no mapmaker, but if someone gives me the flow of the
> dialog I can write the script.
> I could look at adding util
Raphaël Quinet wrote:
> On Tue, 15 Aug 2006 22:39:59 +0800, Lalo Martins <[EMAIL PROTECTED]> wrote:
>
>> On Tue, 15 Aug 2006 11:40:46 +0200, Raphaël Quinet wrote:
>>
>>> One thing that could be added in the "nice to have" list is the
>>> support for migrating local branches to another repo
On Tue, 15 Aug 2006 22:39:59 +0800, Lalo Martins <[EMAIL PROTECTED]> wrote:
> On Tue, 15 Aug 2006 11:40:46 +0200, Raphaël Quinet wrote:
> > One thing that could be added in the "nice to have" list is the
> > support for migrating local branches to another repository.
>
> That's easy; all distribu
Raphaël Quinet wrote:
> One thing that could be added in the "nice to have" list is the
> support for migrating local branches to another repository. This
> would only apply to the systems that support local branches. So the
> choices could be "Easy", "Hard" or "Not applicable". Or maybe just
>
On Mon, 14 Aug 2006 15:19:22 -0600, Alex Schultz wrote:
> Ok, I just made up a table of the criteria that Mark listed, and a
> couple others, for CVS, SVN, Mercurial, Bzr, and Darcs (anyone want any
> others on the table?). If anyone has any revisions or wants to add any
> other SCMs feel free to m
On Tue, 15 Aug 2006 11:40:46 +0200, Raphaël Quinet wrote:
> One thing that could be added in the "nice to have" list is the
> support for migrating local branches to another repository. This
> would only apply to the systems that support local branches. So the
> choices could be "Easy", "Hard" or
On Mon, 14 Aug 2006 15:19:22 -0600, Alex Schultz <[EMAIL PROTECTED]> wrote:
> Ok, I just made up a table of the criteria that Mark listed, and a
> couple others, for CVS, SVN, Mercurial, Bzr, and Darcs (anyone want any
> others on the table?). If anyone has any revisions or wants to add any
> other
On Mon, 14 Aug 2006 22:56:15 -0700, Mark Wedel <[EMAIL PROTECTED]> wrote:
> Alex Schultz wrote:
> > Indeed, that is an issue that prevents it from being usable on sf.net,
> > though I have heard that project space of some other free hosts does
> > allow this sort of usage, though I am unsure of if
I won't comment on the priority, just other things :)
> Better NPC logic 1.x?1
Can be scripted. I'm no mapmaker, but if someone gives me the flow of the
dialog I can write the script.
I could look at adding utility functions to help write such dialogs, to
With crossfire release methodology slowly moving forward (I think one way or
another we'll have figured out what we're doing in terms of a SCCS system by
weeks end), I thought it was time to look at some of the TODO lists. Most of
these are from the wiki or one in the server directory
I wan
Just a note - I've put a copy of this document, with a few minor changes, on
the wiki:
http://wiki.metalforge.net/doku.php/crossfire_release_cycle
___
crossfire mailing list
crossfire@metalforge.org
http://mailman.metalforge.org/mailman/listinfo/cro
13 matches
Mail list logo
