Peter,
I'm not really sure (only a few mins ahead of you
github-experience-wise), but it seems like you cannot push to a parent
branch if you don't have the right permissions to their repo. So, in
that case, you have to tell the owner that you'd like him to look at and
incorporate your changes, for which purpose github provides the pull
request functionality. If Dick were to give you the collaborator
permissions you would be able to push directly.
See http://help.github.com/remotes/ under the Pushing section
Chris
Peter A Pilgrim wrote:
On 8 Apr, 01:36, Chris Phelps <[email protected]> wrote:
Peter,
If you view your fork on the github site, you can click "Pull
Request" at the top of the screen. This will let you send to any of the
other forks, then they can do a "git pull" from their client to merge
your changes into their branch. (The only thing that makes any branch
more authoritative than any other is if we treat one that way.)
Chris
Thanks that worked. I forgot about that lesson from the time. You were
too busy helping me get Git set up on my Windows laptop. So one can
only do this from the github web site?
Chris
Peter A Pilgrim wrote:
On Apr 6, 9:48 pm, Chris Phelps <[email protected]> wrote:
I'm sure others will pipe up, but one of the biggest problems we had,
apart from the basics of people learning how to use the tool, was some
nasty merge problems. A couple participants ran into merge problems
which seemed to be caused by cross-platform line ending issues (CRLF vs
LF), which ended up with every line of the file flagged as a conflict.
Tor also ran into some problems with the merges not being resolved
successfully, which resulted in the need to revert and reapply his
changes. Meanwhile, others of us had reasonably smooth sailing,
frequently doing fresh pulls from Dick's branch, with easy merges and
only a few conflicts which were smoothly fixed.
We got around some of these problems by not doing full merges back to
Dick's branch. Though some others had made changes and requested that
Dick pull those in, he decided to wait on that process until he had
other time to learn that part of the process. Other merge problems were
corrected via painfully resolving the merge, or in cases like Tor's, by
copying the changes to another directory, doing a fresh pull, then
merging manually.
We had about 10 developers working on 3-4 files, so this was definitely
a stress test for git and github. Additionally, we did not really have
anyone in the room with extensive experience to rescue us when we ran
into trouble. Issues such as the line endings would probably be solved
through proper configuration settings. Other merge issues could prove
easy enough to deal with once we had a certain amount of experience with
the tool.
For those who want to take a look, the forks in question are in github
"rooted" athttp://github.com/dickwall/ZenWriterFX. Someone with more
github kung fu might even be able to reconstruct some of our troubles
from the changesets.
Hope that helps
Chris
Hi
Incidentally, I have gone back to my stream on github and implement a
DraggableLineBorder.fx component. It sort resizes most of the time a
child node component. However, may be it is me or the FX 1.2 SDK, the
event handling can be flaky.
What is the command from the round up that push my changeset up to
Dick Wall's Repo?
Or what is the command that notified Dick Wall that my changeset was
incoming?
Sorry I cannot remember it all.
http://github.com/dickwall/ZenWriterFX/network
Joey Gibson wrote:
I've been looking at Hg and git a lot lately, and the possibility of
moving from SVN to one of these. I heard the guys mention that they
had problems using Git and/or Github at the roundup, and I would be
extremely interested to hear what the problems were and how you got
around them (assuming you did). I've only used a DVCS in testing, and
haven't actually used one in production, so any insights would be very
valuable.
Joey
--
Blog:http://joeygibson.com
Twitter:http://twitter.com/joeygibson
FriendFeed:http://friendfeed.com/joeygibson
Facebook:http://facebook.com/joeygibson
--
You received this message because you are subscribed to the Google
Groups "The Java Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
