Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Branch merge phase1 #12

Merged
merged 156 commits into from
Nov 24, 2012
Merged

Branch merge phase1 #12

merged 156 commits into from
Nov 24, 2012

Conversation

hollie
Copy link
Owner

@hollie hollie commented Nov 7, 2012

This is the first phase of merrgin insteon and master. In this phase I bring all changes of master that are not in insteon to the insteon branch.

When this is done, bringing insteon to master should be easy (famous last words TM :-)

I encountered 2 files that did not merge automatically, and I tried to make the best of it. I did not test out the branch to see if it still runs, as I have completely no clue how to test insteon.

The offending files:

  • web/bin/items.pl had edits on the same line that could not be merged automatically. I think that got merged fine manually.
  • lib/xPL_Items,pl had the problem that at a point in time the line endings were changed and hence the file could not be merged automatically. I solved this by taking the master version and setting the line ending to unix again. Hope this turns out fine. By the way: git has a way to convert line endings automatically, if you don't use the regular line endings, please configure this in your git settings!

gliming and others added 30 commits March 8, 2010 11:15
…each

  time it happens (by default mh only shows you the error in details the
  first time, for _any_ module and then that's it).

- show how many times an error was triggered

- add a module_allowed_errors variable to allow each module to set
  how many times they can error out before they get kicked out of the main
  loop (default was and still is 10, but not it's actually clear what's
  going on).
  For instance, I have:
  omnistat_allowed_errors = 999999999999
  hvac_allowed_errors = 999999999999
…within has_link method. Thanks to Eloy P. for bug fix.
a good part of Insteon.pm is going to be re-written, so it may not
be a good use of anyone's time to look to deeply into the current
Insteon.pm code.
* Improve stripping of end of line comments in .mht files.
* Missing rename of triggers_save to _triggers_save in web page code.
* Remove stray vim swap file.
* lib/Omnistat.pm updates by Marc.
…if a cached object already exists. Necessary when mh reloads.
gliming and others added 23 commits March 9, 2012 16:32
…essage to an object. Avoid the possibility of accidental processing for an unsent message.
… CMU Language Toolkit for buiding the language files. This new version is much better with the binary language file support.
famille <famille@famille-simon.com>
…e android devices. Previously, only the last android device register would get these events. Update the android_server module to support the new android_xml subroutine which provides more advanced xml feature for android application support.
…which provide additional xml capabilities for android application support.
…n too long. This prevents a rouge problems with occupancy which I havn't been able to resolve in any better wway.
Provide human readable NACK messages.  Implement Insteon get_engine_vers...
 Need to carry over cmd2 data for nacks.
This change adds the android_callerid method. Call this message with
a callerid Name and Number.  This will result in a callerid popup
message and notification to be sent to the android.  The android
application can be configured to act on the message or ignore.
Add support for callerid pop up message and notification.
Conflicts:
	lib/xPL_Items.pm
	web/bin/items.pl
@jduda
Copy link
Collaborator

jduda commented Nov 8, 2012

On 11/07/2012 04:14 PM, Lieven Hollevoet wrote:

This is the first phase of merrgin insteon and master. In this phase I
bring all changes of master that are not in insteon to the insteon
branch.

When this is done, bringing insteon to master should be easy (famous
last words TM :-)

I encountered 2 files that did not merge automatically, and I tried to
make the best of it. I did not test out the branch to see if it still
runs, as I have completely no clue how to test insteon.

The offending files:

  • web/bin/items.pl had edits on the same line that could not be
    merged automatically. I think that got merged fine manually.
  • lib/xPL_Items,pl had the problem that at a point in time the line
    endings were changed and hence the file could not be merged
    automatically. I solved this by taking the master version and
    setting the line ending to unix again. Hope this turns out fine.
    By the way: git has a way to convert line endings automatically,
    if you don't use the regular line endings, please configure this
    in your git settings!

    You can merge this Pull Request by running:

git pull https://github.com/hollie/misterhouse branch_merge_phase1

Or view, comment on, or merge it at:

Did I do this correctly? I used a fresh git pull to avoid messing up my
working sandbox.

 92    19:41    git clone https://github.com/hollie/misterhouse.git 

mh-git-upstream
93 19:42 cd mh-git-upstream/
96 19:43 git checkout -b insteon origin/insteon
98 19:43 git pull https://github.com/hollie/misterhouse
branch_merge_phase1v

I then started mh-git-upstream directory live. It all seems to be
working fine. Obviously, I can only test the things I use, and of
course Insteon itself.

I also did a directory diff using meld and I don't see any drastic
differences.

Regards,

Jim

@hollie
Copy link
Owner Author

hollie commented Nov 8, 2012

Hi Jim,

On Thu, Nov 8, 2012 at 1:52 AM, Jim Duda notifications@github.com wrote:

Did I do this correctly? I used a fresh git pull to avoid messing up my
working sandbox.

92 19:41 git clone https://github.com/hollie/misterhouse.git
mh-git-upstream
93 19:42 cd mh-git-upstream/
96 19:43 git checkout -b insteon origin/insteon
98 19:43 git pull https://github.com/hollie/misterhouse
branch_merge_phase1v

The last git-pull operation should have resulted in some output showing you
what files are being updated.

Also 'git status' should show you 'your branch is xx commits ahead of
origin/insteon'.

Finally: if your current working copy has a README.md file in the root,
then you're most probably looking at the correct version. I added this file
to the master branch when I imported the project and not to insteon. The
branch_merge_phase1 branch should add it to your insteon branch.

Kind regards,
Lieven.

@jduda
Copy link
Collaborator

jduda commented Nov 8, 2012

On 11/08/2012 03:04 AM, Lieven Hollevoet wrote:

The last git-pull operation should have resulted in some output showing you
what files are being updated.

Also 'git status' should show you 'your branch is xx commits ahead of
origin/insteon'.

Finally: if your current working copy has a README.md file in the root,
then you're most probably looking at the correct version. I added this file
to the master branch when I imported the project and not to insteon. The
branch_merge_phase1 branch should add it to your insteon branch.

Lieven,

Thank you. Yes indeed, this all checks out as you described.

Regards,

Jim

@marcmerlin marcmerlin merged commit 8dba152 into master Nov 24, 2012
hplato added a commit that referenced this pull request Aug 30, 2017
hplato pushed a commit that referenced this pull request Dec 7, 2019
@hplato hplato mentioned this pull request Dec 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants