@Toni: No I didn't push yet. But will do this probably this evening. Looks like EGit is capable of selecting the local branch.
2010/9/18 Toni Menzel <[email protected]> > @Achim: > Did "push" already ? Because i don't that on the timeline at [1]. > I think - don't know the EGit - you pushed you local master (git command > would be "git push origin master"). > - and not your branch. > So, try to make sure that you push your changed branch (webSecureContext) > and not the (probably unchanged) master. > The git command would be: "git push origin webSecureContext". > > @All: > Another model on how we could work is the "normal" github model - which > would look like this: > When interested in changing/working on some project, go to the project [2], > press "fork". > You will end up with a forked copy of that project in your "account" (so > the adress would look like [3]). > Then you work like before (checkout locally, change, commit, push. ) > When you are done, initiate a pull from github web UI ( click on "Pull > Request" when on [4] ) > > This is the really scalable way that git (as i experienced it) promotes. > That would mean contributors don't need to wait for added karma on their > github account. > But as a downside, this does include layer of indirection to ops4j > contributions. Which ( i think ) does not work with the ops4j idea. > > Toni > > [1] https://github.com/organizations/ops4j > [2] http://github.com/ops4j/org.ops4j.pax.web > [3] git://github.com/<user>/org.ops4j.pax.web > [4] http://github.com/<user>/org.ops4j.pax.web > > > On Fri, Sep 17, 2010 at 11:26 PM, Achim Nierbeck > <[email protected]>wrote: > >> Well, I just did the following. >> Grabed a copy of pax-web from git with the eclipse git-plugin (most >> convenient right now) >> made a local branch called webSecureContext applied the patch and did a >> commit. >> So I guess, I successfully did a commit on my local repo, which isn't >> synchronized yet. >> To sync my local branch I just need to do a push, am I right? >> This is my first walk in those new shiny "Git"- shoes >> >> >> ok, you now can push directly to all ops4j repos. >> Are you familar with git ? For starters, there are plenty of helpful docs >> and snippets on github. >> >> >> On Fri, Sep 17, 2010 at 10:02 PM, Achim Nierbeck <[email protected] >> > wrote: >> >>> Just created an account: ANierbeck >>> Thanks >>> >>> Am 17.09.2010 21:53, schrieb Toni Menzel: >>> >>> Do you have a github account already ? >>> I'll then will add you to the list with full access. >>> After checking out the git repo you should be able to do something like >>> the following: >>> >>> svn diff > /tmp/patch.diff >>> >>> cd /path/to/git/repo >>> >>> patch -p0 < /tmp/patch.diff >>> >>> If you have trouble, don't hesitate to ask here. >>> This process is just being fleshed out, and you are part of the operation >>> now. ;) >>> >>> Toni >>> >>> On Fri, Sep 17, 2010 at 9:21 PM, Achim Nierbeck <[email protected] >>> > wrote: >>> >>>> Hi, >>>> since I do work on Issue http://issues.ops4j.org/browse/PAXWEB-210 >>>> what is the best way of switching my working copy to the git repository? >>>> >>>> >>>> >>>> I've created a git mirror for pax-web at github. >>>>> >>>>> I intend to experiment migrating pax-web to jetty7 and i'd rather do >>>>> that in a git branch for now ... >>>>> >>>>> >>>>> >>>> >>>> >>>> _______________________________________________ >>>> general mailing list >>>> [email protected] >>>> http://lists.ops4j.org/mailman/listinfo/general >>>> >>> >>> >>> >>> -- >>> *Toni Menzel || **http://okidokiteam.com* >>> >>> >>> >> >> >> -- >> *Toni Menzel || **http://okidokiteam.com* >> >> >> > > > -- > *Toni Menzel || **http://okidokiteam.com* > >
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
