[socal-piggies] PWC Project - MOVED to bitbucket.org/socal.piggies/pwc/

[Silfheed]

Heyas Grig

I think your right in that you dont need step 2.  Essentially that command
makes a copy of code-snippets to code-snippets-gg and if you do hg push in
code-snippets-gg, it will still push to the socal.piggies/code-snippets/
repo.

If you want your own repo separate from the socal.piggies/code-snippets that
you can push to without the code being pushed to
socal.piggies/code-snippets, you would use the fork command at the top of
the repo overview page just below the Admin tab.  This will create a copy of
the code-snippets repo in your bitbucket account (griggheo) from which you
would then call the clone command on your machine ( $ hg clone
https://griggheo@bitbucket.org/griggheo/code-snippets/<http://bitbucket.org/socal.piggies/code-snippets/>).


Then after you are ready to add your code to the socal.piggies repo, you
would then use 'pull request' to let the socal.piggie user know that your
repo is ready to be merged into the socal.piggies repo.

Again, I'm assuming a lot of this is similar to github.

Luke

On Fri, Jan 22, 2010 at 3:06 PM, Grig Gheorghiu <grig.gheorghiu at gmail.com>wrote:

> I added a tornado_utils subdirectory with the tornado_service_mgr.py
> file I showed at the last meeting. Here are the commands I used, for
> reference:
>
> 1) Cloned repository to a local directory on my laptop:
>
> $ hg clone https://griggheo@bitbucket.org/socal.piggies/code-snippets/
>
> (this created a code-snippets directory which was initially empty)
>
> 2) Cloned this repository to another local copy, so I can make
> modifications in my local clone:
>
> $ hg clone code-snippets  code-snippets-gg
>
> 3) Created directory and file inside my new repository:
>
> $ cd code-snippets-gg
> $ mkdir tornado_utils
> $ cp /from/somewhere/tornado_service_mgr.py tornado_utils
>
> 4) Added directory and file to the repository and committed my changes:
>
> $ hg add tornado_utils
> $ hg commit (at this point I was prompted for a commit message)
>
> 5) Pushed my changes back to the central repository at bitbucket,org
> (note that my current directory was code-snippets-gg at this point):
>
> $ hg push https://griggheo@bitbucket.org/socal.piggies/code-snippets/
>
> I'm not sure if step 2 was absolutely necessary. Maybe just creating a
> new directory/file inside code-snippets, then pushing the changes back
> to bitbucket would have been enough. I'm still getting used to
> mercurial.
>
> Grig
>
>
>
>
> On Fri, Jan 22, 2010 at 2:05 PM, Silfheed <silfheed at gmail.com> wrote:
> > Sure, I've created a branch code-snippets at
> > bitbucket.org/socal.piggies/code-snippets/.
> >
> > If you want to add code, you'll need a bitbucket account and have your
> > account added to the repo as a writer.  Those that have access to the pwc
> > repo have access to the code-snippets repo.
> >
> > Luke
> >
> > On Fri, Jan 22, 2010 at 12:27 PM, Andrew Kou <andrew.kou at gmail.com>
> wrote:
> >>
> >> Hi Luke,
> >>
> >>
> >> Can you please create a code repository for code we look at/discuss
> during
> >> our meetings using that account as well ?
> >>
> >>
> >> Thanks,
> >>
> >> - Andrew
> >>
> >> On Fri, Jan 22, 2010 at 11:54 AM, Grig Gheorghiu
> >> <grig.gheorghiu at gmail.com> wrote:
> >>>
> >>> Thanks, Luke.
> >>>
> >>> Now we need to check some code in ;-)
> >>>
> >>> On Fri, Jan 22, 2010 at 11:51 AM, Silfheed <silfheed at gmail.com> wrote:
> >>> > Heyas
> >>> >
> >>> > So instead of having the pwc code in my personal account, I've
> created
> >>> > a
> >>> > separate account socal.piggies and moved the wiki there.  There wasnt
> >>> > any
> >>> > real code to move over, so there's nothing missing.
> >>> >
> >>> > The project page is now at bitbucket.org/socal.piggies/pwc/wiki/Home
> .
> >>> > Hopefully it's early enough in the project that this doesn't
> completely
> >>> > screw everyone up.  If you had write access to the previous project,
> >>> > you
> >>> > have access to the current project as well.
> >>> >
> >>> > Luke
> >>> >
> >>> > _______________________________________________
> >>> > socal-piggies mailing list
> >>> > socal-piggies at lists.idyll.org
> >>> > http://lists.idyll.org/listinfo/socal-piggies
> >>> >
> >>> >
> >>>
> >>> _______________________________________________
> >>> socal-piggies mailing list
> >>> socal-piggies at lists.idyll.org
> >>> http://lists.idyll.org/listinfo/socal-piggies
> >>
> >>
> >> _______________________________________________
> >> socal-piggies mailing list
> >> socal-piggies at lists.idyll.org
> >> http://lists.idyll.org/listinfo/socal-piggies
> >>
> >
> >
> > _______________________________________________
> > socal-piggies mailing list
> > socal-piggies at lists.idyll.org
> > http://lists.idyll.org/listinfo/socal-piggies
> >
> >
>
> _______________________________________________
> socal-piggies mailing list
> socal-piggies at lists.idyll.org
> http://lists.idyll.org/listinfo/socal-piggies
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idyll.org/pipermail/socal-piggies/attachments/20100122/7969b278/attachment.htm>