Re: Repository

: > >> Hello everyone! I am new here and I am unable to find the repository can >> someone help me out please. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)"

Re: Repository

How can help you? On Sat, 9 Jan, 2021, 9:08 pm Akanksha Shah, wrote: > Hello everyone! I am new here and I am unable to find the repository can > someone help me out please. > > -- > You received this message because you are subscribed to the Google Groups > "Django devel

Repository

Hello everyone! I am new here and I am unable to find the repository can someone help me out please. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop

Re: Removing old branches from the Django Git repository.

ring cleaning? > > >> > > >> I guess maybe it’s sentimental value, and nobody would ever check > > >> them out, but still... > > >> > > >> Tom > > >> > > >> On 10 Oct 2019, at 20:15, Adam Johnson

Re: Removing old branches from the Django Git repository.

t; > >> On 10 Oct 2019, at 20:15, Adam Johnson wrote: > >> > >> Can we leave magic-removal as a tag since it’s such a pivotal > >> point in djangos history? xD > >> > >> On Thu, 10 Oct 2019 at 19:09, Mariusz Felisiak > >&

Re: Removing old branches from the Django Git repository.

till... >> >> Tom >> >> On 10 Oct 2019, at 20:15, Adam Johnson wrote: >> >> Can we leave magic-removal as a tag since it’s such a pivotal point in >> djangos history? xD >> >> On Thu, 10 Oct 2019 at 19:09, Mariusz Felisiak >> wrote: >

Re: Removing old branches from the Django Git repository.

magic-removal as a tag since it’s such a pivotal point in > djangos history? xD > > On Thu, 10 Oct 2019 at 19:09, Mariusz Felisiak > wrote: > >> Hi y'all, >> >> We're going to remove some old branches from the Django Git >> repository on 1st Nove

Re: Removing old branches from the Django Git repository.

Oct 2019, at 20:15, Adam Johnson wrote: > >  > Can we leave magic-removal as a tag since it’s such a pivotal point in > djangos history? xD > >> On Thu, 10 Oct 2019 at 19:09, Mariusz Felisiak >> wrote: >> Hi y'all, >> >> We're going

Re: Removing old branches from the Django Git repository.

Can we leave magic-removal as a tag since it’s such a pivotal point in djangos history? xD On Thu, 10 Oct 2019 at 19:09, Mariusz Felisiak wrote: > Hi y'all, > > We're going to remove some old branches from the Django Git repository > on 1st November 2019: > >

Removing old branches from the Django Git repository.

Hi y'all, We're going to remove some old branches from the Django Git repository on 1st November 2019: - *9* old branches related with Google SOC projects: - soc2009/admin-ui - soc2009/http-wsgi-improvements - soc2009/i18n-improvements - soc2009/model-

Re: GitHub Issues for DEP repository?

On Wed, May 11, 2016 at 1:11 PM, Carl Meyer wrote: > So I'd personally be > fine with a PR to amend this section to remove mention of private > contact. Jacob, I think you wrote this (or adapted it from PEP 1) -- any > thoughts? > I don't recall why that's in there; I'm guessing it came over ver

Re: GitHub Issues for DEP repository?

issue was too minor for a mailing list > discussion, and there was no open pull request to comment on. My first > instinct was to file a GitHub issue (and DEP 1 says "you can submit > corrections as GitHub issues") but it seems that Issues has been > disabled for this reposito

GitHub Issues for DEP repository?

request to comment on. My first instinct was to file a GitHub issue (and DEP 1 says "you can submit corrections as GitHub issues") but it seems that Issues has been disabled for this repository. Was that just an oversight? More broadly, I think that DEP 1 makes this subject too complicat

Re: remove old SVN branches from git repository?

I see these branches are documented: https://docs.djangoproject.com/en/dev/internals/git/#feature-development-branches. In reading that I saw the mention about a grafts file. I don't entirely understand what that does but when I was reading about it, I saw "As of Git 1.6.5, the more flexible g

Re: remove old SVN branches from git repository?

I'd like to keep them around somewhere. Even if it's just a wiki page which links to the last commits of each branch. When you have a local checkout of a brach that checkout is staying even if the branch is removed on a remote. Also your local references to remote branches are kept unless you cal

Re: remove old SVN branches from git repository?

On Wednesday 24 February 2016 22:46:38 Tim Graham wrote: > They're already in everyone's forks too unless you delete them. True, but I think we should keep them accessible under the project roof. Shai.

Re: remove old SVN branches from git repository?

They're already in everyone's forks too unless you delete them. Not sure if deleting them from the main repo would delete them for all forks too. On Wednesday, February 24, 2016 at 3:36:53 PM UTC-5, Florian Apolloner wrote: > > > > On Wednesday, February 24, 2016 at 9:12:19 PM UTC+1, Shai Berger

Re: remove old SVN branches from git repository?

On Wednesday, February 24, 2016 at 9:12:19 PM UTC+1, Shai Berger wrote: > > If they're a nuisance, I suggest that we clone the Django repo into > another > one under the django organization -- say, "django-historical-branches" -- > before removing them from the main repo. > I was about to s

Re: remove old SVN branches from git repository?

before removing them from the main repo. Shai. On Wednesday 24 February 2016 17:45:43 Tim Graham wrote: > Will anyone miss these branches if we remove them from the repository? I > presume they've all either been merged or are so outdated that there isn't > value in keeping them

remove old SVN branches from git repository?

Will anyone miss these branches if we remove them from the repository? I presume they've all either been merged or are so outdated that there isn't value in keeping them. attic/boulder-oracle-sprint attic/full-history attic/generic-auth attic/gis attic/i18n attic/magic-removal attic/

Re: Is Django documentation translations to land in main repository ?

On Saturday, December 15, 2012 5:05:36 AM UTC+1, Russell Keith-Magee wrote: > > > On Sat, Dec 15, 2012 at 11:53 AM, Amirouche B. > > > wrote: > >> Héllo, >> >> Everything is in the title. Does Django core dev's want to have localized >> docume

Re: Is Django documentation translations to land in main repository ?

On Sat, Dec 15, 2012 at 11:53 AM, Amirouche B. wrote: > Héllo, > > Everything is in the title. Does Django core dev's want to have localized > documentation in main repository or should it be managed by local DUG ? > Yes :-) In a perfect world, you'd be able to g

Is Django documentation translations to land in main repository ?

Héllo, Everything is in the title. Does Django core dev's want to have localized documentation in main repository or should it be managed by local DUG ? Thanks to Pilot Systems, I improved a bit the french documentation [1] basically what I've done is converted it to use the Sphinx

A quick primer on how to move feature branches to the new Git repository

I have posted instructions on how to easily and safely rebase feature branches from an old fork of Django's SVN mirror onto Django's official git repository. I hope this helps. Let me know if you need help or the instructions are unclear or incorrect. https://gist.github.com/2549844

Re: Experimental Git repository available

On Thu, Jun 19, Jacob Kaplan-Moss wrote: > On Thu, Jun 19, 2008 at 11:55 AM, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > > Is this only going to offer the trunk branch? > > Until I learn more about Git, yes :) > > If you know the correct incantation to add other git-svn-created > branches,

Re: Experimental Git repository available

On 19 Jun 2008, at 6:07 pm, Jacob Kaplan-Moss wrote: > If you know the correct incantation to add other git-svn-created > branches, feel free to school me :) I think Brian Rosner covered pulling in all branches from svn on his screencast about django and git [0] but I can't off the top of my

Re: Experimental Git repository available

gt;> Yeah, hgsvn is one-way, > > > H > > >>hg help convert > > hg convert [OPTION]... SOURCE [DEST [REVMAP]] > > > Convert a foreign SCM repository to a Mercurial one. > > True, but that doesn't address pushing changes back to SVN, at least

Re: Experimental Git repository available

Marc Fargas wrote: > El jue, 19-06-2008 a las 14:03 -0700, Michael Elsdörfer escribió: >> FWIW (I'm currently playing around with all three of them), bazaar >> appears to support pushing into svn as well. > > Yes, with bzr-svn. Be advised, though, that currently bzr-svn will dump out a ton of sv

Re: Experimental Git repository available

El jue, 19-06-2008 a las 17:14 -0500, Jeremy Dunck escribió: > git-svn init -s http://code.djangoproject.com/svn/ git-svn init -s http://code.djangoproject.com/svn/django Unless you want djangoproject.com also ;) signature.asc Description: Esta parte del mensaje está firmada digitalmente

Re: Experimental Git repository available

On 6/19/08, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > Please don't try to turn this into a "Django should use > Git!" thread; if you do I'll just ignore you. We're not switching from > SVN any time in the foreseeable future. I hope you are nearsighted and the foreseeable future isn't too

Re: Experimental Git repository available

On Thu, Jun 19, 2008 at 5:02 PM, Rob Hudson <[EMAIL PROTECTED]> wrote: > > On 6/19/08, Rob Hudson <[EMAIL PROTECTED]> wrote: >> Use the `-T`, `-t`, `-b` flags, or `-s` if the project has a "standard >> layout". This should bring over branches and tags as well. Oh, er, uh, I didn't notice only t

Re: Experimental Git repository available

On 6/19/08, Rob Hudson <[EMAIL PROTECTED]> wrote: > Use the `-T`, `-t`, `-b` flags, or `-s` if the project has a "standard > layout". This should bring over branches and tags as well. I forgot to reference the man page (which was in my clipboard): http://www.kernel.org/pub/software/scm/git/docs

Re: Experimental Git repository available

On 6/19/08, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > On Thu, Jun 19, 2008 at 11:55 AM, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > > Is this only going to offer the trunk branch? > > > Until I learn more about Git, yes :) > > If you know the correct incantation to add other git-sv

Re: Experimental Git repository available

On Thu, Jun 19, 2008 at 4:27 PM, Marc Fargas <[EMAIL PROTECTED]> wrote: > El jue, 19-06-2008 a las 14:03 -0700, Michael Elsdörfer escribió: >> FWIW (I'm currently playing around with all three of them), bazaar >> appears to support pushing into svn as well. > > Yes, with bzr-svn. Didn't play too mu

Re: Experimental Git repository available

El jue, 19-06-2008 a las 14:03 -0700, Michael Elsdörfer escribió: > FWIW (I'm currently playing around with all three of them), bazaar > appears to support pushing into svn as well. Yes, with bzr-svn. Didn't play too much with that one. But Bazaar is slow, *really* slow. -- http://www.marcfargas

Re: Experimental Git repository available

> Yeah, hgsvn is one-way, which git-svn has the "dcommit" command > which'll commit back to SVN. I'm really not much of a git fan, but > git-svn makes a better svn than svn does, if you know what I mean. FWIW (I'm currently playing around with all three of them), bazaar appears to support pushing

Re: Experimental Git repository available

> Something like this? > http://hg.dpaste.com/django/ Yeah I use that one at the moment, I was getting at a more thing. I'm sure that's more difficult to do with HG then GIT and like Jacob said, it's a moot point anyway :-) Ben 2008/6/19 Ariel Mauricio Nunez Gomez

Re: Experimental Git repository available

I'm just guessing, but I think git-clone doesn't pull in remotes, so that our clones are getting whatever's your master, hence trunk. You can make a local copy of a remote branch like so: git-checkout -b local/branchname branchname There's no magic in the "local" prefix, it's just to distinguish

Re: Experimental Git repository available

RCE [DEST [REVMAP]] > > Convert a foreign SCM repository to a Mercurial one. True, but that doesn't address pushing changes back to SVN, at least not practically. Mercurial's own docs [1] admit this is a problem needing improvement. Compare that with git-svn's dcommit c

Re: Experimental Git repository available

You're a gentleman and a scholar, Jacob. I think you'll find that git is a tool that feels good in the hand. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send emai

Re: Experimental Git repository available

ht in thinking that support of SVN <=> HG >> is less complete than GIT <=> SVN? > > Yeah, hgsvn is one-way, H >hg help convert hg convert [OPTION]... SOURCE [DEST [REVMAP]] Convert a foreign SCM repository to a Mercurial one. ... Accepted destination formats:

Re: Experimental Git repository available

On Thu, Jun 19, 2008 at 11:39 AM, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > I've published an experimental Git clone of Django's SVN repository > (created with git-svn). If you're a Git user and want to use this > repository, be my guest. Please still upload pat

Re: Experimental Git repository available

On Thu, Jun 19, 2008 at 11:59 AM, Ben Ford <[EMAIL PROTECTED]> wrote: > This sounds like a nice idea... Any plans to do a mercurial repo (a-la the > documentation refactor)? Am I right in thinking that support of SVN <=> HG > is less complete than GIT <=> SVN? Yeah, hgsvn is one-way, which git-sv

Re: Experimental Git repository available

On Thu, Jun 19, 2008 at 11:55 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Is this only going to offer the trunk branch? Until I learn more about Git, yes :) If you know the correct incantation to add other git-svn-created branches, feel free to school me :) Jacob --~--~-~--~

Re: Experimental Git repository available

Something like this? http://hg.dpaste.com/django/ --~--~-~--~~~---~--~~ 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 unsubscribe from

Re: Experimental Git repository available

only going to offer the trunk branch? > > On Jun 19, 11:39 am, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> > wrote: > > Hi folks -- > > > > I've published an experimental Git clone of Django's SVN repository > > (created with git-svn). If you&

Re: Experimental Git repository available

Is this only going to offer the trunk branch? On Jun 19, 11:39 am, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> wrote: > Hi folks -- > > I've published an experimental Git clone of Django's SVN repository > (created with git-svn). If you're a Git user and

Experimental Git repository available

Hi folks -- I've published an experimental Git clone of Django's SVN repository (created with git-svn). If you're a Git user and want to use this repository, be my guest. Please still upload patches to Trac for review, but mention you're using my clone so I can more easily ap

GSoC 2007: Package management and public application repository

core by using the distutils and setuptools modules. Additionally I want to build a public application repository website with standard community features (nicely implemented by the django-* apps) with bindings to the CheeseShop/ PyPI, Python's central software repository. The general goal is

PyCon BoF about Content Repository

Hello, I have added a BoF in the PyCon wiki for the next session in Dallas. It's about having a standard in Python for content repositories, that could be used by any Python framework, like Django. http://us.pycon.org/TX2007/PyJCR Please react/participate on the wiki, if you think this could b

Re: Proposal: Django Apps & Project Repository (again)

Ian Holsman wrote: > luckily? for me I have a bit of time on my hands tomorrow and > possibly monday. > i could get a start on something 'forgish' which could then be used > to critique/improve on. Ian, does this mean you are working on a DjangoForge written in Django? --~--~-~--~~-

Re: Proposal: Django Apps & Project Repository (again)

On 8/24/06, Ian Holsman <[EMAIL PROTECTED]> wrote: > > > On 24/08/2006, at 2:00 PM, limodou wrote: > > > > > On 8/24/06, Ian Holsman <[EMAIL PROTECTED]> wrote: > >> > >> so Limodou. > >> > >> what's the next step. > >> have you got a prototype of it ? or a idea on how it will work? > >> I've got a

Re: Proposal: Django Apps & Project Repository (again)

On 24/08/2006, at 2:00 PM, limodou wrote: > > On 8/24/06, Ian Holsman <[EMAIL PROTECTED]> wrote: >> >> so Limodou. >> >> what's the next step. >> have you got a prototype of it ? or a idea on how it will work? >> I've got a old linux box you can use to host it until it gets >> popular. > > No,

Re: Proposal: Django Apps & Project Repository (again)

On 8/24/06, Ian Holsman <[EMAIL PROTECTED]> wrote: > > so Limodou. > > what's the next step. > have you got a prototype of it ? or a idea on how it will work? > I've got a old linux box you can use to host it until it gets popular. No, I haven't a plan about it, just some ideas. If someone make i

Re: Proposal: Django Apps & Project Repository (again)

because every djangor can easy find it. I think the first >>> stage could be the index site supplied by django site, and the exact >>> projects could be found everywhere. And the second stage could be >>> hosting the most django relative projects in django repository si

Re: Proposal: Django Apps & Project Repository (again)

te, and the exact > > projects could be found everywhere. And the second stage could be > > hosting the most django relative projects in django repository site. > > As for a first stage, the djangoproject wiki would work. For example, > a contributed middleware page a

Re: Proposal: Django Apps & Project Repository (again)

age could be > hosting the most django relative projects in django repository site. As for a first stage, the djangoproject wiki would work. For example, a contributed middleware page already exists: http://code.djangoproject.com/wiki/ContributedMiddleware --~--~-~--~~~-

Re: Proposal: Django Apps & Project Repository (again)

I've added the code.google link on the wiki :) In general people will host their projects at google, sourceforge and other sites like these. The basic thing what djangoproject.com should have is a project catalog where all django based projects can be added, listed, searched etc. Second thing - t

Re: Proposal: Django Apps & Project Repository (again)

I agree with you what absolutely need to be included to the dajngo web site is at least a pointer to the code repository. It would also be nice if djangoproject could host the project documentation. However I think that it would be great to have a sandbox for each project where visitor can

Re: Proposal: Django Apps & Project Repository (again)

ngor can easy find it. I think the first stage could be the index site supplied by django site, and the exact projects could be found everywhere. And the second stage could be hosting the most django relative projects in django repository site. -- I like python! My Blog: http://www.donews.net/lim

Re: Proposal: Django Apps & Project Repository (again)

Hello, I have the feeling that this is more or less already existing. It is called "google code" - http://code.google.com/hosting/search?q=label:django It is taking 2 min to create a new projet. the only thing missing there is a "meta" wiki where the owner of each project can publish informatio

Re: Proposal: Django Apps & Project Repository (again)

gt; limodou wrote: > > > There are some threads talking about the apps repository already, but > > > till now, no repository be found. So I want to suggest again: we > > > should build an official project web site to host django apps or > > > projects. So we can ea

Re: Proposal: Django Apps & Project Repository (again)

On 8/23/06, Gary Wilson <[EMAIL PROTECTED]> wrote: > > limodou wrote: > > There are some threads talking about the apps repository already, but > > till now, no repository be found. So I want to suggest again: we > > should build an official project web site to ho

Re: Proposal: Django Apps & Project Repository (again)

limodou wrote: > There are some threads talking about the apps repository already, but > till now, no repository be found. So I want to suggest again: we > should build an official project web site to host django apps or > projects. So we can easy share our source code and exchan

Re: Proposal: Django Apps & Project Repository (again)

On 8/20/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi limodou, > > limodou schrieb: > > There are some threads talking about the apps repository already, but > > till now, no repository be found. So I want to suggest again: we > > should build an offi

Re: Proposal: Django Apps & Project Repository (again)

Hi limodou, limodou schrieb: > There are some threads talking about the apps repository already, but > till now, no repository be found. So I want to suggest again: we > should build an official project web site to host django apps or > projects. So we can easy share our source code

Proposal: Django Apps & Project Repository (again)

There are some threads talking about the apps repository already, but till now, no repository be found. So I want to suggest again: we should build an official project web site to host django apps or projects. So we can easy share our source code and exchange our ideas. And I think 0.95 is stable