On Sat, Jul 14, 2007 at 05:19:57PM -0700, Brian Harring wrote:
> On Fri, Jul 13, 2007 at 11:28:27PM -0500, Gary Wilson wrote:
> >
> > Brian Harring wrote:
> > > On Wed, Jul 11, 2007 at 09:38:54AM -0500, Deryck Hodge wrote:
> > >> For example:
> > >>
> > >> mkdir repos
> > >> cd repos
> > >> bzr in
On Fri, Jul 13, 2007 at 11:28:27PM -0500, Gary Wilson wrote:
>
> Brian Harring wrote:
> > On Wed, Jul 11, 2007 at 09:38:54AM -0500, Deryck Hodge wrote:
> >> For example:
> >>
> >> mkdir repos
> >> cd repos
> >> bzr init
> >> svn co http://code.djangoproject.com/svn/django/trunk/ django_trunk
> >>
Brian Harring wrote:
> On Wed, Jul 11, 2007 at 09:38:54AM -0500, Deryck Hodge wrote:
>> For example:
>>
>> mkdir repos
>> cd repos
>> bzr init
>> svn co http://code.djangoproject.com/svn/django/trunk/ django_trunk
>> bzr add django_trunk
>> bzr commit
>>
>> Then you can bzr branch from there to ha
On 7/13/07, koenb <[EMAIL PROTECTED]> wrote:
> Maybe I am missing something here.
Nah -- not really; I understand (and agree with) your objections.
We're just gonna give this different method a try for a time and see
how it works out.
Jacob
--~--~-~--~~~---~--~~
On 11 jul, 16:12, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]>
wrote:
> On 7/11/07, Ben Ford <[EMAIL PROTECTED]> wrote:
>
> > None as yet, I'm really keen to get it back into the svn repo, but I think
> > the people concerned are busy with other things at the moment.
>
> I've said this a couple times
On 7/11/07, Brian Harring <[EMAIL PROTECTED]> wrote:
> On Wed, Jul 11, 2007 at 09:38:54AM -0500, Deryck Hodge wrote:
> >
> > On 7/11/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> > > The best thing to do is host your changes remotely. That way there's
> > > no implicit assumptions about if an
On 7/11/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On 7/11/07, Deryck Hodge <[EMAIL PROTECTED]> wrote:
> > Also, it might be worth the project's time to pick a distributed VCS
> > and host mirrors on djangoproject.com.
>
> Tom's Mercurial mirror is basically the official DVCS version of
On Wed, Jul 11, 2007 at 09:38:54AM -0500, Deryck Hodge wrote:
>
> On 7/11/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> > The best thing to do is host your changes remotely. That way there's
> > no implicit assumptions about if and when it'll get merged into
> > Django.
> >
>
> Hi, Jacob.
>
On 7/11/07, Deryck Hodge <[EMAIL PROTECTED]> wrote:
> Also, it might be worth the project's time to pick a distributed VCS
> and host mirrors on djangoproject.com.
Tom's Mercurial mirror is basically the official DVCS version of
Django; if it gets popular at all we'll probably move it onto
django
On Wed, Jul 11, 2007 at 09:43:15PM +0700, Ben Ford wrote:
> I'm already happily using SVK, and was originally planning to use it to
> remotely host the multi-db branch on my virtual server... However the only
> info
> I could find on achieving this was incorrect and I'm not sure if it is even
> po
Forest,
I'm already happily using SVK, and was originally planning to use it to
remotely host the multi-db branch on my virtual server... However the only
info I could find on achieving this was incorrect and I'm not sure if it is
even possible to split repos (onto 2 different machine), which is wh
On 7/11/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> The best thing to do is host your changes remotely. That way there's
> no implicit assumptions about if and when it'll get merged into
> Django.
>
Hi, Jacob.
I'll mention Bazaar, too. My experience with it has been very pleasant.
I get
On Wed, Jul 11, 2007 at 09:12:14AM -0500, Jacob Kaplan-Moss wrote:
> Probably the best way to host an "unofficial" branch would be by using
> Tom's Mercurial mirror of Django trunk:
> http://hg.korpios.com/django.trunk/.
Since you're on svn, you might also try svk.
-Forest
signature.asc
Descrip
On 7/11/07, Ben Ford <[EMAIL PROTECTED]> wrote:
> None as yet, I'm really keen to get it back into the svn repo, but I think
> the people concerned are busy with other things at the moment.
I've said this a couple times, but I guess it's been missed:
We're moving away from giving branch access s
Hi,
None as yet, I'm really keen to get it back into the svn repo, but I think
the people concerned are busy with other things at the moment. I can send
you the patch if you like and I'll chase them up again.
Ben
On 11/07/07, koenb <[EMAIL PROTECTED]> wrote:
>
>
> Is there any news on updating the
Is there any news on updating the svn repo for this branch ?
k
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To u
Hi all,
I've now got the multiple-db-support branch fully merged up to date with
trunk (as of rev 5559). As I've mentioned before it's in a mirrored repo, so
I could commit all of the changesets incrementally back into the django svn
repo (I've done 4 separate merges so far). I think that this appr
17 matches
Mail list logo
