ranch

Valiant Eagle, Inc. (OTC:PSRU) Acquires Franchise X Entertainment LLC, A Full-Service Record Label and Artist Management Company

By www.24-7pressrelease.com
Published On :: Fri, 21 Feb 2020 07:00:00 GMT

Valiant Eagle Inc. (OTC:PSRU) is pleased to announce that it acquired Franchise X Entertainment LLC, a full-service record label and artist management company.


Full Article

ranch

Alsco Naples Branch Offers Support to the Naples Shelter for Abused Women and Children

By www.24-7pressrelease.com
Published On :: Tue, 05 May 2020 07:00:00 GMT

Aid helps support and protect some of the community's most vulnerable members through advocacy, empowerment and social change


Full Article

ranch

IFPG's Niche Publication, Franchise Consultant Magazine, Offers a Unique Educational Tool for Franchise Consultants

By www.24-7pressrelease.com
Published On :: Fri, 13 Mar 2020 07:00:00 GMT


Full Article

ranch

CashYourCarUAE Launches New Branch in The Springs Souk

By www.24-7pressrelease.com
Published On :: Sun, 08 Dec 2019 07:00:00 GMT

The new location offers extra convenience for customers to sell cars in Dubai.


Full Article

ranch

Bloodlines: Nadal Poised To Extend His Branch Of Arch Sire Line

By www.paulickreport.com
Published On :: Tue, 05 May 2020 16:33:20 +0000

Is Arch (by Kris S.) trying to construct his own male line, bridging time and space and fashion? The effort of Grade 1 Arkansas Derby winner Nadal (by the Arch stallion Blame) suggests that this is not out of the realm of possibility, although Arch, one of the supremely solid sires of the breed, left […]

The post Bloodlines: Nadal Poised To Extend His Branch Of Arch Sire Line appeared first on Horse Racing News | Paulick Report.


Full Article

ranch

Grand Canyon to Replace and Relocate Underground Electric Cable at Phantom Ranch

By www.nps.gov
Published On :: Thu, 13 Dec 2012 10:45:00 EST

Grand Canyon National Park will be replacing and relocating the underground electric cable that serves Phantom Ranch in early 2013. https://www.nps.gov/grca/learn/news/2012-12-13_phanton-construction.htm


Full Article

ranch

Pipeline Break in Grand Canyon National Park Leads to Water Shortage at Phantom Ranch

By www.nps.gov
Published On :: Fri, 28 Jun 2013 02:49:00 EST

As a result of a series of breaks in the Trans-Canyon Water Pipeline, Phantom Ranch at the bottom of Grand Canyon is currently experiencing a water shortage. Visitors hiking to Phantom Ranch must be self-sufficient and be prepared to carry or treat all drinking water. https://www.nps.gov/grca/learn/news/pipeline-break-in-grand-canyon.htm


Full Article

ranch

UPDATE Pipeline Break in Grand Canyon National Park Results in Continued Suspension of Phantom Ranch Operations

By www.nps.gov
Published On :: Fri, 28 Jun 2013 13:26:00 EST

Pipeline Break in Grand Canyon National Park Results in Continued Suspension of Phantom Ranch Operations https://www.nps.gov/grca/learn/news/update-pipeline-break-in-grand-canyon-national-park-results-in-continued-suspension-of-phantom-ranch-operations.htm


Full Article

ranch

Update: Pipeline Repair Complete at Grand Canyon National Park –Services Resume at Phantom Ranch

By www.nps.gov
Published On :: Sat, 29 Jun 2013 13:04:00 EST

Grand Canyon National Park staff have completed repairs to the Trans-Canyon Water Pipeline. Crews are monitoring the re-pressurization of the pipeline, which should be completed by noon on Sunday, June 30. Xanterra South Rim LLC will resume operations Sunday; guests at Phantom Ranch are being advised that water restrictions may resume if another break occurs during re-pressurization. https://www.nps.gov/grca/learn/news/update-pipeline-repair-complete-at-grand-canyon-national-park-services-resume-at-phantom-ranch.htm


Full Article

ranch

Water Shortage at Phantom Ranch Caused by pipeline Break

By www.nps.gov
Published On :: Thu, 11 Dec 2014 06:36:00 EST

Visitors hiking to Phantom Ranch must be self-sufficient and be prepared to carry or treat all drinking water. A break in the Trans-Canyon Water Pipeline and inclement weather delaying equipment from reaching repair crews, has resulted in a water shortage at Phantom Ranch at the bottom of Grand Canyon. https://www.nps.gov/grca/learn/news/20141211_pipeline-break-phantom.htm


Full Article

ranch

Update: Pipeline Repair Complete at Grand Canyon National Park –Services Resume at Phantom Ranch

By www.nps.gov
Published On :: Sat, 13 Dec 2014 09:34:00 EST

Grand Canyon National Park staff have completed repairs to the Trans-Canyon Water Pipeline. Water restrictions have been lifted and Xanterra South Rim LLC has resumed normal operations. https://www.nps.gov/grca/learn/news/13dec2014-pipelinerepair.htm


Full Article

ranch

Grand Canyon to Replace Portion of Trans-Canyon Pipeline at Phantom Ranch

By www.nps.gov
Published On :: Fri, 23 Jan 2015 04:44:00 EST

Grand Canyon National Park will begin replacing a portion of the Trans-Canyon Pipeline at Phantom Ranch beginning on Monday, January 26, 2015. https://www.nps.gov/grca/learn/news/replace-portion-tcp.htm


Full Article

ranch

Construction Continues on Transcanyon Pipeline Replacement at Phantom Ranch

By www.nps.gov
Published On :: Thu, 30 Apr 2015 09:21:00 EST

Replacement of the Transcanyon Pipeline at Phantom Ranch has progressed and the contractor has replaced over a quarter mile of pipeline. https://www.nps.gov/grca/learn/news/construction-continues-on-transcanyon-pipeline-replacement-at-phantom-ranch.htm


Full Article

ranch

Test Well Installation at Phantom Ranch March 29 to April 5, 2018

By www.nps.gov
Published On :: Tue, 27 Mar 2018 11:18:00 EST

On March 29, 2018, the National Park Service (NPS) will begin installing one test well and two monitoring wells next to Bright Angel Creek near Phantom Ranch. https://www.nps.gov/grca/learn/news/test-wells.htm


Full Article

ranch

Silvies Valley Ranch, OR: using artificial beaver dams to restore incised streams

By www.fs.fed.us
Published On :: Wed, 01 Nov 2017 08:00:00 PST

The Silvies Valley Ranch is an example of using local innovation to combat the global problem of incised streams on rangelands. Incised channels reduce the flow between water in the channel and water in the surrounding soils, which reduces the vegetation available for wildlife habitat and cattle forage. One of the ranch owners, Scott Campbell, a doctor of veterinary medicine, believes that stream incision is related to the decline of beaver populations; thus, the ranch’s approach to restoration includes efforts to mimic beavers’ influence on the system. He is using an extensive network of low-rise dams made from locally available materials (dirt, gravel, rock, and logs), commonly referred to as “artificial beaver dams” (ABDs). Campbell said that the ABDs on the ranch successfully increased stream connectivity to their floodplains and increased the quantity and forage quality of wet meadows on the property, with no changes in where cattle were grazing. The experiences of this landowner exemplify a unique approach that provides a model for others facing similar challenges to doing restoration on private land. The transformation taking place on the Silvies Valley Ranch has garnered the attention of neighboring ranch owners, some of whom are beginning to experiment with similar restoration technologies. Campbell would like to continue installing structures, but has encountered numerous roadblocks in the permitting process. He has since taken an active role in building legislative support for the ABD technology being used on the ranch, and in facilitating its adoption in other places. This case study—based on interviews with stakeholders involved in the Silvies Valley Ranch project—highlights the social benefits and challenges experienced by one rancher using ABDs as a restoration tool, and provides insights for improving their use in the future. It is part of a larger interdisciplinary study that explores the potential of different beaver-related restoration approaches for achieving watershed restoration and livestock production goals on rangelands in the Western United States.


Full Article

ranch

Committed to the wrong branch? -, @{upstream}, and @{-1} to the rescue

By feedproxy.google.com
Published On :: Thu, 27 Feb 2020 00:00:00 -0500

I get into this situation sometimes. Maybe you do too. I merge feature work into a branch used to collect features, and then continue development but on that branch instead of back on the feature branch

git checkout feature
# ... bunch of feature commits ...
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# deploy qa-environment to the QA remote environment
# ... more feature commits ...
# oh. I'm not committing in the feature branch like I should be

and have to move those commits to the feature branch they belong in and take them out of the throwaway accumulator branch

git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

Maybe you prefer

git branch -D qa-environment
git checkout qa-environment

over

git checkout qa-environment
git reset --hard origin/qa-environment

Either way, that works. But it'd be nicer if we didn't have to type or even remember the branches' names and the remote's name. They are what is keeping this from being a context-independent string of commands you run any time this mistake happens. That's what we're going to solve here.

Shorthands for longevity

I like to use all possible natively supported shorthands. There are two broad motivations for that.

  1. Fingers have a limited number of movements in them. Save as many as possible left late in life.
  2. Current research suggests that multitasking has detrimental effects on memory. Development tends to be very heavy on multitasking. Maybe relieving some of the pressure on quick-access short term memory (like knowing all relevant branch names) add up to leave a healthier memory down the line.

First up for our scenario: the - shorthand, which refers to the previously checked out branch. There are a few places we can't use it, but it helps a lot:

Bash 
# USING -

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit -        # ????
git push
# hack hack hack
# whoops
git checkout -        # now on feature ???? 
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout - # now on qa-environment ????
git reset --hard origin/qa-environment
git merge --no-ff --no-edit -        # ????
git checkout -                       # ????
# on feature and ready for more feature commits
Bash 
# ORIGINAL

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# hack hack hack
# whoops
git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

We cannot use - when cherry-picking a range

> git cherry-pick origin/-..-
fatal: bad revision 'origin/-..-'

> git cherry-pick origin/qa-environment..-
fatal: bad revision 'origin/qa-environment..-'

and even if we could we'd still have provide the remote's name (here, origin).

That shorthand doesn't apply in the later reset --hard command, and we cannot use it in the branch -D && checkout approach either. branch -D does not support the - shorthand and once the branch is deleted checkout can't reach it with -:

# assuming that branch-a has an upstream origin/branch-a
> git checkout branch-a
> git checkout branch-b
> git checkout -
> git branch -D -
error: branch '-' not found.
> git branch -D branch-a
> git checkout -
error: pathspec '-' did not match any file(s) known to git

So we have to remember the remote's name (we know it's origin because we are devoting memory space to knowing that this isn't one of those times it's something else), the remote tracking branch's name, the local branch's name, and we're typing those all out. No good! Let's figure out some shorthands.

@{-<n>} is hard to say but easy to fall in love with

We can do a little better by using @{-<n>} (you'll also sometimes see it referred to be the older @{-N}). It is a special construct for referring to the nth previously checked out ref.

> git checkout branch-a
> git checkout branch-b
> git rev-parse --abbrev-rev @{-1} # the name of the previously checked out branch
branch-a
> git checkout branch-c
> git rev-parse --abbrev-rev @{-2} # the name of branch checked out before the previously checked out one
branch-a

Back in our scenario, we're on qa-environment, we switch to feature, and then want to refer to qa-environment. That's @{-1}! So instead of

git cherry-pick origin/qa-environment..qa-environment

We can do

git cherry-pick origin/qa-environment..@{-1}

Here's where we are (🎉 marks wins from -, 💥 marks the win from @{-1})

Bash 
# USING - AND @{-1}

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit -                # ????
git push
# hack hack hack
# whoops
git checkout -                               # ????
git cherry-pick origin/qa-environment..@{-1} # ????
git push
git checkout -                               # ????
git reset --hard origin/qa-environment
git merge --no-ff --no-edit -                # ????
git checkout -                               # ????
# ready for more feature commits
Bash 
# ORIGINAL

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# hack hack hack
# whoops
git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

One down, two to go: we're still relying on memory for the remote's name and the remote branch's name and we're still typing both out in full. Can we replace those with generic shorthands?

@{-1} is the ref itself, not the ref's name, we can't do

> git cherry-pick origin/@{-1}..@{-1}
origin/@{-1}
fatal: ambiguous argument 'origin/@{-1}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

because there is no branch origin/@{-1}. For the same reason, @{-1} does not give us a generalized shorthand for the scenario's later git reset --hard origin/qa-environment command.

But good news!

Do @{u} @{push}

@{upstream} or its shorthand @{u} is the remote branch a that would be pulled from if git pull were run. @{push} is the remote branch that would be pushed to if git push was run.

> git checkout branch-a
Switched to branch 'branch-a'
Your branch is ahead of 'origin/branch-a' by 3 commits.
  (use "git push" to publish your local commits)
> git reset --hard origin/branch-a
HEAD is now at <the SHA origin/branch-a is at>

we can

> git checkout branch-a
Switched to branch 'branch-a'
Your branch is ahead of 'origin/branch-a' by 3 commits.
  (use "git push" to publish your local commits)
> git reset --hard @{u}                                # <-- So Cool!
HEAD is now at <the SHA origin/branch-a is at>

Tacking either onto a branch name will give that branch's @{upstream} or @{push}. For example

git checkout branch-a@{u}

is the branch branch-a pulls from.

In the common workflow where a branch pulls from and pushes to the same branch, @{upstream} and @{push} will be the same, leaving @{u} as preferable for its terseness. @{push} shines in triangular workflows where you pull from one remote and push to another (see the external links below).

Going back to our scenario, it means short, portable commands with a minimum human memory footprint. (🎉 marks wins from -, 💥 marks the win from @{-1}, 😎 marks the wins from @{u}.)

Bash 
# USING - AND @{-1} AND @{u}

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit -    # ????
git push
# hack hack hack
# whoops
git checkout -                   # ????
git cherry-pick @{-1}@{u}..@{-1} # ????????
git push
git checkout -                   # ????
git reset --hard @{u}            # ????
git merge --no-ff --no-edit -    # ????
git checkout -                   # ????
# ready for more feature commits
Bash 
# ORIGINAL

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# hack hack hack
# whoops
git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

Make the things you repeat the easiest to do

Because these commands are generalized, we can run some series of them once, maybe

git checkout - && git reset --hard @{u} && git checkout -

or

git checkout - && git cherry-pick @{-1}@{u}.. @{-1} && git checkout - && git reset --hard @{u} && git checkout -

and then those will be in the shell history just waiting to be retrieved and run again the next time, whether with CtrlR incremental search or history substring searching bound to the up arrow or however your interactive shell is configured. Or make it an alias, or even better an abbreviation if your interactive shell supports them. Save the body wear and tear, give memory a break, and level up in Git.

And keep going

The GitHub blog has a good primer on triangular workflows and how they can polish your process of contributing to external projects.

The FreeBSD Wiki has a more in-depth article on triangular workflow process (though it doesn't know about @{push} and @{upstream}).

The construct @{-<n>} and the suffixes @{push} and @{upstream} are all part of the gitrevisions spec. Direct links to each:


    Full Article

    • Code
    • Front-end Engineering
    • Back-end Engineering
    ranch

    Committed to the wrong branch? -, @{upstream}, and @{-1} to the rescue

    By feedproxy.google.com
    Published On :: Thu, 27 Feb 2020 00:00:00 -0500

    I get into this situation sometimes. Maybe you do too. I merge feature work into a branch used to collect features, and then continue development but on that branch instead of back on the feature branch

    git checkout feature
# ... bunch of feature commits ...
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# deploy qa-environment to the QA remote environment
# ... more feature commits ...
# oh. I'm not committing in the feature branch like I should be

    and have to move those commits to the feature branch they belong in and take them out of the throwaway accumulator branch

    git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

    Maybe you prefer

    git branch -D qa-environment
git checkout qa-environment

    over

    git checkout qa-environment
git reset --hard origin/qa-environment

    Either way, that works. But it'd be nicer if we didn't have to type or even remember the branches' names and the remote's name. They are what is keeping this from being a context-independent string of commands you run any time this mistake happens. That's what we're going to solve here.

    Shorthands for longevity

    I like to use all possible natively supported shorthands. There are two broad motivations for that.

    1. Fingers have a limited number of movements in them. Save as many as possible left late in life.
    2. Current research suggests that multitasking has detrimental effects on memory. Development tends to be very heavy on multitasking. Maybe relieving some of the pressure on quick-access short term memory (like knowing all relevant branch names) add up to leave a healthier memory down the line.

    First up for our scenario: the - shorthand, which refers to the previously checked out branch. There are a few places we can't use it, but it helps a lot:

    Bash 
    # USING -

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit -        # ????
git push
# hack hack hack
# whoops
git checkout -        # now on feature ???? 
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout - # now on qa-environment ????
git reset --hard origin/qa-environment
git merge --no-ff --no-edit -        # ????
git checkout -                       # ????
# on feature and ready for more feature commits
    Bash 
    # ORIGINAL

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# hack hack hack
# whoops
git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

    We cannot use - when cherry-picking a range

    > git cherry-pick origin/-..-
fatal: bad revision 'origin/-..-'

> git cherry-pick origin/qa-environment..-
fatal: bad revision 'origin/qa-environment..-'

    and even if we could we'd still have provide the remote's name (here, origin).

    That shorthand doesn't apply in the later reset --hard command, and we cannot use it in the branch -D && checkout approach either. branch -D does not support the - shorthand and once the branch is deleted checkout can't reach it with -:

    # assuming that branch-a has an upstream origin/branch-a
> git checkout branch-a
> git checkout branch-b
> git checkout -
> git branch -D -
error: branch '-' not found.
> git branch -D branch-a
> git checkout -
error: pathspec '-' did not match any file(s) known to git

    So we have to remember the remote's name (we know it's origin because we are devoting memory space to knowing that this isn't one of those times it's something else), the remote tracking branch's name, the local branch's name, and we're typing those all out. No good! Let's figure out some shorthands.

    @{-<n>} is hard to say but easy to fall in love with

    We can do a little better by using @{-<n>} (you'll also sometimes see it referred to be the older @{-N}). It is a special construct for referring to the nth previously checked out ref.

    > git checkout branch-a
> git checkout branch-b
> git rev-parse --abbrev-rev @{-1} # the name of the previously checked out branch
branch-a
> git checkout branch-c
> git rev-parse --abbrev-rev @{-2} # the name of branch checked out before the previously checked out one
branch-a

    Back in our scenario, we're on qa-environment, we switch to feature, and then want to refer to qa-environment. That's @{-1}! So instead of

    git cherry-pick origin/qa-environment..qa-environment

    We can do

    git cherry-pick origin/qa-environment..@{-1}

    Here's where we are (🎉 marks wins from -, 💥 marks the win from @{-1})

    Bash 
    # USING - AND @{-1}

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit -                # ????
git push
# hack hack hack
# whoops
git checkout -                               # ????
git cherry-pick origin/qa-environment..@{-1} # ????
git push
git checkout -                               # ????
git reset --hard origin/qa-environment
git merge --no-ff --no-edit -                # ????
git checkout -                               # ????
# ready for more feature commits
    Bash 
    # ORIGINAL

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# hack hack hack
# whoops
git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

    One down, two to go: we're still relying on memory for the remote's name and the remote branch's name and we're still typing both out in full. Can we replace those with generic shorthands?

    @{-1} is the ref itself, not the ref's name, we can't do

    > git cherry-pick origin/@{-1}..@{-1}
origin/@{-1}
fatal: ambiguous argument 'origin/@{-1}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

    because there is no branch origin/@{-1}. For the same reason, @{-1} does not give us a generalized shorthand for the scenario's later git reset --hard origin/qa-environment command.

    But good news!

    Do @{u} @{push}

    @{upstream} or its shorthand @{u} is the remote branch a that would be pulled from if git pull were run. @{push} is the remote branch that would be pushed to if git push was run.

    > git checkout branch-a
Switched to branch 'branch-a'
Your branch is ahead of 'origin/branch-a' by 3 commits.
  (use "git push" to publish your local commits)
> git reset --hard origin/branch-a
HEAD is now at <the SHA origin/branch-a is at>

    we can

    > git checkout branch-a
Switched to branch 'branch-a'
Your branch is ahead of 'origin/branch-a' by 3 commits.
  (use "git push" to publish your local commits)
> git reset --hard @{u}                                # <-- So Cool!
HEAD is now at <the SHA origin/branch-a is at>

    Tacking either onto a branch name will give that branch's @{upstream} or @{push}. For example

    git checkout branch-a@{u}

    is the branch branch-a pulls from.

    In the common workflow where a branch pulls from and pushes to the same branch, @{upstream} and @{push} will be the same, leaving @{u} as preferable for its terseness. @{push} shines in triangular workflows where you pull from one remote and push to another (see the external links below).

    Going back to our scenario, it means short, portable commands with a minimum human memory footprint. (🎉 marks wins from -, 💥 marks the win from @{-1}, 😎 marks the wins from @{u}.)

    Bash 
    # USING - AND @{-1} AND @{u}

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit -    # ????
git push
# hack hack hack
# whoops
git checkout -                   # ????
git cherry-pick @{-1}@{u}..@{-1} # ????????
git push
git checkout -                   # ????
git reset --hard @{u}            # ????
git merge --no-ff --no-edit -    # ????
git checkout -                   # ????
# ready for more feature commits
    Bash 
    # ORIGINAL

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# hack hack hack
# whoops
git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

    Make the things you repeat the easiest to do

    Because these commands are generalized, we can run some series of them once, maybe

    git checkout - && git reset --hard @{u} && git checkout -

    or

    git checkout - && git cherry-pick @{-1}@{u}.. @{-1} && git checkout - && git reset --hard @{u} && git checkout -

    and then those will be in the shell history just waiting to be retrieved and run again the next time, whether with CtrlR incremental search or history substring searching bound to the up arrow or however your interactive shell is configured. Or make it an alias, or even better an abbreviation if your interactive shell supports them. Save the body wear and tear, give memory a break, and level up in Git.

    And keep going

    The GitHub blog has a good primer on triangular workflows and how they can polish your process of contributing to external projects.

    The FreeBSD Wiki has a more in-depth article on triangular workflow process (though it doesn't know about @{push} and @{upstream}).

    The construct @{-<n>} and the suffixes @{push} and @{upstream} are all part of the gitrevisions spec. Direct links to each:


      Full Article

      • Code
      • Front-end Engineering
      • Back-end Engineering
      ranch

      Committed to the wrong branch? -, @{upstream}, and @{-1} to the rescue

      By feedproxy.google.com
      Published On :: Thu, 27 Feb 2020 00:00:00 -0500

      I get into this situation sometimes. Maybe you do too. I merge feature work into a branch used to collect features, and then continue development but on that branch instead of back on the feature branch

      git checkout feature
# ... bunch of feature commits ...
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# deploy qa-environment to the QA remote environment
# ... more feature commits ...
# oh. I'm not committing in the feature branch like I should be

      and have to move those commits to the feature branch they belong in and take them out of the throwaway accumulator branch

      git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

      Maybe you prefer

      git branch -D qa-environment
git checkout qa-environment

      over

      git checkout qa-environment
git reset --hard origin/qa-environment

      Either way, that works. But it'd be nicer if we didn't have to type or even remember the branches' names and the remote's name. They are what is keeping this from being a context-independent string of commands you run any time this mistake happens. That's what we're going to solve here.

      Shorthands for longevity

      I like to use all possible natively supported shorthands. There are two broad motivations for that.

      1. Fingers have a limited number of movements in them. Save as many as possible left late in life.
      2. Current research suggests that multitasking has detrimental effects on memory. Development tends to be very heavy on multitasking. Maybe relieving some of the pressure on quick-access short term memory (like knowing all relevant branch names) add up to leave a healthier memory down the line.

      First up for our scenario: the - shorthand, which refers to the previously checked out branch. There are a few places we can't use it, but it helps a lot:

      Bash 
      # USING -

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit -        # ????
git push
# hack hack hack
# whoops
git checkout -        # now on feature ???? 
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout - # now on qa-environment ????
git reset --hard origin/qa-environment
git merge --no-ff --no-edit -        # ????
git checkout -                       # ????
# on feature and ready for more feature commits
      Bash 
      # ORIGINAL

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# hack hack hack
# whoops
git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

      We cannot use - when cherry-picking a range

      > git cherry-pick origin/-..-
fatal: bad revision 'origin/-..-'

> git cherry-pick origin/qa-environment..-
fatal: bad revision 'origin/qa-environment..-'

      and even if we could we'd still have provide the remote's name (here, origin).

      That shorthand doesn't apply in the later reset --hard command, and we cannot use it in the branch -D && checkout approach either. branch -D does not support the - shorthand and once the branch is deleted checkout can't reach it with -:

      # assuming that branch-a has an upstream origin/branch-a
> git checkout branch-a
> git checkout branch-b
> git checkout -
> git branch -D -
error: branch '-' not found.
> git branch -D branch-a
> git checkout -
error: pathspec '-' did not match any file(s) known to git

      So we have to remember the remote's name (we know it's origin because we are devoting memory space to knowing that this isn't one of those times it's something else), the remote tracking branch's name, the local branch's name, and we're typing those all out. No good! Let's figure out some shorthands.

      @{-<n>} is hard to say but easy to fall in love with

      We can do a little better by using @{-<n>} (you'll also sometimes see it referred to be the older @{-N}). It is a special construct for referring to the nth previously checked out ref.

      > git checkout branch-a
> git checkout branch-b
> git rev-parse --abbrev-rev @{-1} # the name of the previously checked out branch
branch-a
> git checkout branch-c
> git rev-parse --abbrev-rev @{-2} # the name of branch checked out before the previously checked out one
branch-a

      Back in our scenario, we're on qa-environment, we switch to feature, and then want to refer to qa-environment. That's @{-1}! So instead of

      git cherry-pick origin/qa-environment..qa-environment

      We can do

      git cherry-pick origin/qa-environment..@{-1}

      Here's where we are (🎉 marks wins from -, 💥 marks the win from @{-1})

      Bash 
      # USING - AND @{-1}

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit -                # ????
git push
# hack hack hack
# whoops
git checkout -                               # ????
git cherry-pick origin/qa-environment..@{-1} # ????
git push
git checkout -                               # ????
git reset --hard origin/qa-environment
git merge --no-ff --no-edit -                # ????
git checkout -                               # ????
# ready for more feature commits
      Bash 
      # ORIGINAL

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# hack hack hack
# whoops
git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

      One down, two to go: we're still relying on memory for the remote's name and the remote branch's name and we're still typing both out in full. Can we replace those with generic shorthands?

      @{-1} is the ref itself, not the ref's name, we can't do

      > git cherry-pick origin/@{-1}..@{-1}
origin/@{-1}
fatal: ambiguous argument 'origin/@{-1}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

      because there is no branch origin/@{-1}. For the same reason, @{-1} does not give us a generalized shorthand for the scenario's later git reset --hard origin/qa-environment command.

      But good news!

      Do @{u} @{push}

      @{upstream} or its shorthand @{u} is the remote branch a that would be pulled from if git pull were run. @{push} is the remote branch that would be pushed to if git push was run.

      > git checkout branch-a
Switched to branch 'branch-a'
Your branch is ahead of 'origin/branch-a' by 3 commits.
  (use "git push" to publish your local commits)
> git reset --hard origin/branch-a
HEAD is now at <the SHA origin/branch-a is at>

      we can

      > git checkout branch-a
Switched to branch 'branch-a'
Your branch is ahead of 'origin/branch-a' by 3 commits.
  (use "git push" to publish your local commits)
> git reset --hard @{u}                                # <-- So Cool!
HEAD is now at <the SHA origin/branch-a is at>

      Tacking either onto a branch name will give that branch's @{upstream} or @{push}. For example

      git checkout branch-a@{u}

      is the branch branch-a pulls from.

      In the common workflow where a branch pulls from and pushes to the same branch, @{upstream} and @{push} will be the same, leaving @{u} as preferable for its terseness. @{push} shines in triangular workflows where you pull from one remote and push to another (see the external links below).

      Going back to our scenario, it means short, portable commands with a minimum human memory footprint. (🎉 marks wins from -, 💥 marks the win from @{-1}, 😎 marks the wins from @{u}.)

      Bash 
      # USING - AND @{-1} AND @{u}

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit -    # ????
git push
# hack hack hack
# whoops
git checkout -                   # ????
git cherry-pick @{-1}@{u}..@{-1} # ????????
git push
git checkout -                   # ????
git reset --hard @{u}            # ????
git merge --no-ff --no-edit -    # ????
git checkout -                   # ????
# ready for more feature commits
      Bash 
      # ORIGINAL

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# hack hack hack
# whoops
git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

      Make the things you repeat the easiest to do

      Because these commands are generalized, we can run some series of them once, maybe

      git checkout - && git reset --hard @{u} && git checkout -

      or

      git checkout - && git cherry-pick @{-1}@{u}.. @{-1} && git checkout - && git reset --hard @{u} && git checkout -

      and then those will be in the shell history just waiting to be retrieved and run again the next time, whether with CtrlR incremental search or history substring searching bound to the up arrow or however your interactive shell is configured. Or make it an alias, or even better an abbreviation if your interactive shell supports them. Save the body wear and tear, give memory a break, and level up in Git.

      And keep going

      The GitHub blog has a good primer on triangular workflows and how they can polish your process of contributing to external projects.

      The FreeBSD Wiki has a more in-depth article on triangular workflow process (though it doesn't know about @{push} and @{upstream}).

      The construct @{-<n>} and the suffixes @{push} and @{upstream} are all part of the gitrevisions spec. Direct links to each:


        Full Article

        • Code
        • Front-end Engineering
        • Back-end Engineering
        ranch

        Committed to the wrong branch? -, @{upstream}, and @{-1} to the rescue

        By feedproxy.google.com
        Published On :: Thu, 27 Feb 2020 00:00:00 -0500

        I get into this situation sometimes. Maybe you do too. I merge feature work into a branch used to collect features, and then continue development but on that branch instead of back on the feature branch

        git checkout feature
# ... bunch of feature commits ...
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# deploy qa-environment to the QA remote environment
# ... more feature commits ...
# oh. I'm not committing in the feature branch like I should be

        and have to move those commits to the feature branch they belong in and take them out of the throwaway accumulator branch

        git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

        Maybe you prefer

        git branch -D qa-environment
git checkout qa-environment

        over

        git checkout qa-environment
git reset --hard origin/qa-environment

        Either way, that works. But it'd be nicer if we didn't have to type or even remember the branches' names and the remote's name. They are what is keeping this from being a context-independent string of commands you run any time this mistake happens. That's what we're going to solve here.

        Shorthands for longevity

        I like to use all possible natively supported shorthands. There are two broad motivations for that.

        1. Fingers have a limited number of movements in them. Save as many as possible left late in life.
        2. Current research suggests that multitasking has detrimental effects on memory. Development tends to be very heavy on multitasking. Maybe relieving some of the pressure on quick-access short term memory (like knowing all relevant branch names) add up to leave a healthier memory down the line.

        First up for our scenario: the - shorthand, which refers to the previously checked out branch. There are a few places we can't use it, but it helps a lot:

        Bash 
        # USING -

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit -        # ????
git push
# hack hack hack
# whoops
git checkout -        # now on feature ???? 
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout - # now on qa-environment ????
git reset --hard origin/qa-environment
git merge --no-ff --no-edit -        # ????
git checkout -                       # ????
# on feature and ready for more feature commits
        Bash 
        # ORIGINAL

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# hack hack hack
# whoops
git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

        We cannot use - when cherry-picking a range

        > git cherry-pick origin/-..-
fatal: bad revision 'origin/-..-'

> git cherry-pick origin/qa-environment..-
fatal: bad revision 'origin/qa-environment..-'

        and even if we could we'd still have provide the remote's name (here, origin).

        That shorthand doesn't apply in the later reset --hard command, and we cannot use it in the branch -D && checkout approach either. branch -D does not support the - shorthand and once the branch is deleted checkout can't reach it with -:

        # assuming that branch-a has an upstream origin/branch-a
> git checkout branch-a
> git checkout branch-b
> git checkout -
> git branch -D -
error: branch '-' not found.
> git branch -D branch-a
> git checkout -
error: pathspec '-' did not match any file(s) known to git

        So we have to remember the remote's name (we know it's origin because we are devoting memory space to knowing that this isn't one of those times it's something else), the remote tracking branch's name, the local branch's name, and we're typing those all out. No good! Let's figure out some shorthands.

        @{-<n>} is hard to say but easy to fall in love with

        We can do a little better by using @{-<n>} (you'll also sometimes see it referred to be the older @{-N}). It is a special construct for referring to the nth previously checked out ref.

        > git checkout branch-a
> git checkout branch-b
> git rev-parse --abbrev-rev @{-1} # the name of the previously checked out branch
branch-a
> git checkout branch-c
> git rev-parse --abbrev-rev @{-2} # the name of branch checked out before the previously checked out one
branch-a

        Back in our scenario, we're on qa-environment, we switch to feature, and then want to refer to qa-environment. That's @{-1}! So instead of

        git cherry-pick origin/qa-environment..qa-environment

        We can do

        git cherry-pick origin/qa-environment..@{-1}

        Here's where we are (🎉 marks wins from -, 💥 marks the win from @{-1})

        Bash 
        # USING - AND @{-1}

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit -                # ????
git push
# hack hack hack
# whoops
git checkout -                               # ????
git cherry-pick origin/qa-environment..@{-1} # ????
git push
git checkout -                               # ????
git reset --hard origin/qa-environment
git merge --no-ff --no-edit -                # ????
git checkout -                               # ????
# ready for more feature commits
        Bash 
        # ORIGINAL

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# hack hack hack
# whoops
git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

        One down, two to go: we're still relying on memory for the remote's name and the remote branch's name and we're still typing both out in full. Can we replace those with generic shorthands?

        @{-1} is the ref itself, not the ref's name, we can't do

        > git cherry-pick origin/@{-1}..@{-1}
origin/@{-1}
fatal: ambiguous argument 'origin/@{-1}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'

        because there is no branch origin/@{-1}. For the same reason, @{-1} does not give us a generalized shorthand for the scenario's later git reset --hard origin/qa-environment command.

        But good news!

        Do @{u} @{push}

        @{upstream} or its shorthand @{u} is the remote branch a that would be pulled from if git pull were run. @{push} is the remote branch that would be pushed to if git push was run.

        > git checkout branch-a
Switched to branch 'branch-a'
Your branch is ahead of 'origin/branch-a' by 3 commits.
  (use "git push" to publish your local commits)
> git reset --hard origin/branch-a
HEAD is now at <the SHA origin/branch-a is at>

        we can

        > git checkout branch-a
Switched to branch 'branch-a'
Your branch is ahead of 'origin/branch-a' by 3 commits.
  (use "git push" to publish your local commits)
> git reset --hard @{u}                                # <-- So Cool!
HEAD is now at <the SHA origin/branch-a is at>

        Tacking either onto a branch name will give that branch's @{upstream} or @{push}. For example

        git checkout branch-a@{u}

        is the branch branch-a pulls from.

        In the common workflow where a branch pulls from and pushes to the same branch, @{upstream} and @{push} will be the same, leaving @{u} as preferable for its terseness. @{push} shines in triangular workflows where you pull from one remote and push to another (see the external links below).

        Going back to our scenario, it means short, portable commands with a minimum human memory footprint. (🎉 marks wins from -, 💥 marks the win from @{-1}, 😎 marks the wins from @{u}.)

        Bash 
        # USING - AND @{-1} AND @{u}

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit -    # ????
git push
# hack hack hack
# whoops
git checkout -                   # ????
git cherry-pick @{-1}@{u}..@{-1} # ????????
git push
git checkout -                   # ????
git reset --hard @{u}            # ????
git merge --no-ff --no-edit -    # ????
git checkout -                   # ????
# ready for more feature commits
        Bash 
        # ORIGINAL

git checkout feature
# hack hack hack
git push
git checkout qa-environment
git merge --no-ff --no-edit feature
git push
# hack hack hack
# whoops
git checkout feature
git cherry-pick origin/qa-environment..qa-environment
git push
git checkout qa-environment
git reset --hard origin/qa-environment
git merge --no-ff --no-edit feature
git checkout feature
# ready for more feature commits

        Make the things you repeat the easiest to do

        Because these commands are generalized, we can run some series of them once, maybe

        git checkout - && git reset --hard @{u} && git checkout -

        or

        git checkout - && git cherry-pick @{-1}@{u}.. @{-1} && git checkout - && git reset --hard @{u} && git checkout -

        and then those will be in the shell history just waiting to be retrieved and run again the next time, whether with CtrlR incremental search or history substring searching bound to the up arrow or however your interactive shell is configured. Or make it an alias, or even better an abbreviation if your interactive shell supports them. Save the body wear and tear, give memory a break, and level up in Git.

        And keep going

        The GitHub blog has a good primer on triangular workflows and how they can polish your process of contributing to external projects.

        The FreeBSD Wiki has a more in-depth article on triangular workflow process (though it doesn't know about @{push} and @{upstream}).

        The construct @{-<n>} and the suffixes @{push} and @{upstream} are all part of the gitrevisions spec. Direct links to each:


          Full Article

          • Code
          • Front-end Engineering
          • Back-end Engineering
          ranch

          Multitype branching process with nonhomogeneous Poisson and generalized Polya immigration. (arXiv:1909.03684v2 [math.PR] UPDATED)

          By arxiv.org
          Published On ::

          In a multitype branching process, it is assumed that immigrants arrive according to a nonhomogeneous Poisson or a generalized Polya process (both processes are formulated as a nonhomogeneous birth process with an appropriate choice of transition intensities). We show that the renormalized numbers of objects of the various types alive at time $t$ for supercritical, critical, and subcritical cases jointly converge in distribution under those two different arrival processes. Furthermore, some transient moment analysis when there are only two types of particles is provided. AMS 2000 subject classifications: Primary 60J80, 60J85; secondary 60K10, 60K25, 90B15.


          Full Article

          ranch

          Jumanji: The Next Level continues a one-joke franchise that wasn't all that funny to begin with

          By www.inlander.com
          Published On :: Thu, 12 Dec 2019 01:30:00 -0800

          [IMAGE-1]Welcome back to the jungle. And welcome to an unfortunate new Christmas movie tradition: the Jumanji movie.…


          Full Article

          • Film/Film News
          ranch

          As The Rise of Skywalker readies to put a bow on a chapter in Star Wars lore, the franchise's omnipresence has shifted its fandom

          By www.inlander.com
          Published On :: Thu, 19 Dec 2019 01:30:00 -0800

          With all due respect to Greta Thunberg and Billie Eilish, nobody had a better 2019 than Baby Yoda. The real star of the Disney+ flagship Star Wars series The Mandalorian, the little green puppeteering/CGI marvel (aka "the Child") might be the most adorable creature ever created.…


          Full Article

          • Film/Film News
          ranch

          Branched hetero polyfunctional polyoxyalkylene compound and intermediate thereof

          By www.freepatentsonline.com
          Published On :: Tue, 12 May 2015 08:00:00 EDT

          A branched hetero polyfunctional polyoxyalkylene compound represented by the following formula (1): wherein Z represents a hydroxyl group-removed residue of pentaerythritol or dipentaerythritol, OA1 and OA2 represent an oxyalkylene group having 2 to 4 carbon atoms, L1, L2 and L3 represent an alkylene group or an alkylene group that contains an ester bond, a urethane bond, an amide bond, an ether bond, a carbonate bond, a secondary amino group or a urea bond, X and Y are different from each other and represent a functional group capable of a chemical reaction; m and n are an average number of moles of the oxyalkylene group added, m represents 5 to 1,000, n represents 0 to 1,000, and p, q and r represent 0 or 1; and s1 is an integer of 2 or more and s1+s2=4 or 6.


          Full Article

          ranch

          Process for producing monobranched fatty acids or alkyl esters

          By www.freepatentsonline.com
          Published On :: Tue, 24 Mar 2015 08:00:00 EDT

          A process for producing C10-C26 monobranched fatty acids or alkyl esters thereof which includes isomerizing unsaturated C10-C26 fatty acids or alkyl esters thereof in the presence of a catalyst which comprises both a zeolite and a Lewis base. The zeolite can be reused after simple separation from the reaction products without having to regenerate. The process is particularly suitable for producing highly monobranched fatty acids or alkyl esters thereof.


          Full Article

          ranch

          Aqueous dispersions of microgel encapsulated particles utilizing hyperbranched acrylic polymers

          By www.freepatentsonline.com
          Published On :: Tue, 26 May 2015 08:00:00 EDT

          An aqueous dispersion includes particles at least partially encapsulated in a microgel where the microgel is prepared from a hyperbranched acrylic polymer. In addition, a method for making an aqueous dispersion includes: (1) mixing in an aqueous medium: (a) particles, (b) at least one ethylenically unsaturated monomer, and (c) a water-dispersible hyperbranched acrylic polymer having ethylenic unsaturation; and (2) polymerizing the at least one ethylenically unsaturated monomer and water-dispersible hyperbranched acrylic polymer having ethylenic unsaturation to at least partially encapsulate the particles in a microgel.


          Full Article

          ranch

          Method for the manufacture of branched saturated hydrocarbons

          By www.freepatentsonline.com
          Published On :: Tue, 26 May 2015 08:00:00 EDT

          The invention relates to a method for the manufacture of branched saturated hydrocarbons, said method comprising the steps where a feed comprising olefins having at least 10 carbons is simultaneously hydrogenated and isomerized in the presence of hydrogen at a temperature of 100-400° C., under hydrogen partial pressure of 0.01-10 MPa, in the presence of a catalyst comprising a metal selected from the metals of Group VIIIb of the Periodic Table of Elements, a molecular sieve selected from ten member ring molecular sieves, twelve member ring molecular sieves and mesoporous molecular sieves embedded with zeolite, and a carrier, to yield branched saturated hydrocarbons.


          Full Article

          ranch

          Multifunctional hyperbranched organic intercalating agent, method for its manufacture and its use

          By www.freepatentsonline.com
          Published On :: Tue, 26 May 2015 08:00:00 EDT

          A facile synthesis of amphiphilic hyperbranched polymers consisting of poly(amic acid) and polyimide was developed via “A2+B3” approach from difunctional anhydride and trifunctional hydrophilic poly(oxyalkylene)triamine. Various amphiphilic hyperbranched poly(amic acid)s (HBPAAs) with terminal amine functionalities and amic acid structures were prepared through ring-opening polyaddition at room temperature, followed by thermal imidization process for the formation of hyperbranched polyimides (HBPIs), accordingly. The resulting HBPIs were analyzed by GPC, indicating the molecule weights of 5000˜7000 g/mol with a distribution of polydispersity between 2.0 and 3.8. The amine titration for HBPIs indicated the peripheral total-amine contents to be 8.32˜18.32 mequiv/g dependent on compositions.


          Full Article

          ranch

          Crosslinkable curing super-branched polyester and cured product and preparation method thereof

          By www.freepatentsonline.com
          Published On :: Tue, 16 Dec 2014 08:00:00 EST

          A crosslinkable curing super-branched polyester and the cured product and the preparation method thereof are disclosed. The super-branched polyester has high refractive index and comprises a compound represented by the following structural formula (I). In the formula (I), HBP is the backbone of the super-branched polyester; both a and b are positive integers; the sum of a and b is less than or equal to n; n is more than or equal to 10 and less than 80. In the super-branched polyester, A is represented by formula (II) and N is represented by formula (III), wherein R is methyl or hydrogen atom; the mole ratio of N relative to the total mole of A and N is more than 30 mol %, and the ratio of the total mole of A and N relative to the product of the total mole of HBP backbone and n is more than 0.5 and less than or equal to 1.


          Full Article

          ranch

          Aqueous epoxy and organo-substituted branched organopolysiloxane emulsions

          By www.freepatentsonline.com
          Published On :: Tue, 31 Mar 2015 08:00:00 EDT

          Aqueous emulsions of epoxy- and organo-substituted, branched organopolysiloxanes are prepared by emulsifying the latter in water with the aid of a dispersing agent. The emulsions are storage stable and are useful in multi-component coating, adhesive, and binder systems.


          Full Article

          ranch

          Combined branch target and predicate prediction for instruction blocks

          By www.freepatentsonline.com
          Published On :: Tue, 28 Apr 2015 08:00:00 EDT

          Embodiments provide methods, apparatus, systems, and computer readable media associated with predicting predicates and branch targets during execution of programs using combined branch target and predicate predictions. The predictions may be made using one or more prediction control flow graphs which represent predicates in instruction blocks and branches between blocks in a program. The prediction control flow graphs may be structured as trees such that each node in the graphs is associated with a predicate instruction, and each leaf associated with a branch target which jumps to another block. During execution of a block, a prediction generator may take a control point history and generate a prediction. Following the path suggested by the prediction through the tree, both predicate values and branch targets may be predicted. Other embodiments may be described and claimed.


          Full Article

          ranch

          Virtualization support for branch prediction logic enable / disable at hypervisor and guest operating system levels

          By www.freepatentsonline.com
          Published On :: Tue, 12 May 2015 08:00:00 EDT

          A hypervisor and one or more guest operating systems resident in a data processing system and hosted by the hypervisor are configured to selectively enable or disable branch prediction logic through separate hypervisor-mode and guest-mode instructions. By doing so, different branch prediction strategies may be employed for different operating systems and user applications hosted thereby to provide finer grained optimization of the branch prediction logic for different operating scenarios.


          Full Article

          ranch

          Branched alkoxylate surfactant composition

          By www.freepatentsonline.com
          Published On :: Tue, 14 Apr 2015 08:00:00 EDT

          A composition is described containing a branched nonionic surfactant of Formula (I): (I) wherein x is a real number from 1 to 11, y is a real number from 1 to 20, R 1 is an alkyl group having 1 to 3 carbon atoms, R 2 is an alkyl group having 4 to 6 carbon atoms, and a primary 5 alcohol ethoxylate.


          Full Article

          ranch

          Branched poly (hydroxy acid) and production process thereof

          By www.freepatentsonline.com
          Published On :: Tue, 24 Mar 2015 08:00:00 EDT

          Process for manufacturing a polymer by polycondensation of a hydroxy acid, said polymer comprising at least 80% by weight of units that correspond to the hydroxy acid, according to which at least one polyfunctional reactant capable of giving rise to the formation of a three-dimensional polymer network is mixed with the hydroxy acid, and according to which the mixture is subjected to temperature and pressure conditions and for a duration which are all suitable for giving rise to the formation of the network. Poly(hydroxy acid) (PHA) obtainable by such a process.


          Full Article

          ranch

          Branching core-pin assembly and system for forming branching channels

          By www.freepatentsonline.com
          Published On :: Tue, 19 May 2015 08:00:00 EDT

          A core-pin assembly composed of a primary core-pin and at least one secondary core-pin. The primary core-pin has a primary core-pin body defining at least one element for coupling with a mating end of at least one secondary core-pin. The secondary core-pin has a mating end and a secondary core-pin body. The mating end is configured to fit with the element defined in the primary core-pin body such that the primary core-pin and the secondary core-pin(s) reversibly join together to form a branching structure. The assembly may further include at least one tertiary core-pin and the secondary core-pin body may define at least one element for coupling with a mating end of at least one tertiary core-pin. The mating end of the tertiary core pin is configured to fit with the secondary core-pin body such that the primary core-pin, secondary and tertiary core-pin(s) reversibly join together forming a branching structure.


          Full Article

          ranch

          Four branched dendrimer-PEG for conjugation to proteins and peptides

          By www.freepatentsonline.com
          Published On :: Tue, 22 Apr 2014 08:00:00 EDT

          A polymeric dendrimer-like structure with four branches of monomethoxy-polyethylene glycol that can be represented as: The carboxylic group of the previous structure can be functionalized for the production of conjugates of pharmaceutical interest. The binding of this dendrimer-like polyethylene glycol to therapeutic proteins improves their in vitro and in vivo stability.


          Full Article

          ranch

          Genes regulating plant branching, promotors, genetic constructs containing same and uses thereof

          By www.freepatentsonline.com
          Published On :: Tue, 26 May 2015 08:00:00 EDT

          The invention relates to genes coding for TCP family transcription factors and having a biological role in the development of axillary buds and branch growth. Furthermore, the invention relates to the promoters of the transcription of said genes, to the genetic constructs containing same and to the uses thereof, including the use of agents that modulate the expression of these genes in order to modify plant architecture.


          Full Article

          ranch

          Three dimensional branchline coupler using through silicon vias and design structures

          By www.freepatentsonline.com
          Published On :: Tue, 19 May 2015 08:00:00 EDT

          A three dimensional (3D) branchline coupler using through silicon vias (TSV), methods of manufacturing the same and design structures are disclosed. The method includes forming a first waveguide structure in a first dielectric material. The method further includes forming a second waveguide structure in a second dielectric material. The method further includes forming through silicon vias through a substrate formed between the first dielectric material and the second dielectric material, which connects the first waveguide structure to the second waveguide structure.


          Full Article

          ranch

          Machine for tying plants, in particular the branches of vines

          By www.freepatentsonline.com
          Published On :: Tue, 17 Jun 2014 08:00:00 EDT

          A machine (1) for tying vegetation, in particular vine, raspberry or similar branches, including a unit (4) for lifting up the branches, an element (5) for supplying tying-up wires (50) and members (7, 8) for binding the tying-up wires. These binding members include two pivoting arms (7, 8) that are mounted to pivot around vertical axes (A) and be moved by jacks. One of the arms (7) comprises an on-board tie magazine (71) that is arranged in the extension of a tying head (72), and the other arm (8) includes an insertion head (82) cooperating with the tying head (72) when the arms (7, 8) are in a working position in order to fit the tie (60) on the tying-up wires (50).


          Full Article

          ranch

          Branched stent/graft and method of fabrication

          By www.freepatentsonline.com
          Published On :: Tue, 18 Feb 2014 08:00:00 EST

          Branched braided stent or graft devices and processes for fabrication of the devices are disclosed in which a trunk portion and two hinge leg portions are fabricated in one piece braided from a single plurality of filaments, whereby the legs contain the full plurality of filaments and the trunk portion contains a subset of the same plurality of filaments. The fabrication process involves braiding the hinged legs on a mandrel while retaining loops of filament between the hinged leg portions for subsequent braiding of the trunk portion of the stent or graft.


          Full Article

          ranch

          Method of treating plant growth media with multi-branched wetting agents

          By www.freepatentsonline.com
          Published On :: Tue, 24 Mar 2015 08:00:00 EDT

          Certain novel formulations of plant growth media additives that act in such a manner as to permit proper amounts of moisture to contact root systems in order to reduce hydrophobicity within said media. The inventive formulation comprising multi-branched surfactant compounds with both hydrophobic and hydrophilic constituents within each branch attached to a polyfunctional base compound permit effective moisture penetration through plant growth media for sustained seedling and plant growth therein. Such multi-branched wetting agents provide sustained moisture penetration over a sustained period of time, since the individual branches of such compounds may become dissociated from its base polyfunctional compound. Since such branches include both hydrophobic and hydrophilic constituents themselves, and thus act as wetting agents, even after degradation of the initial surfactant compound, repeated wetting and moisture penetration, at least, are permitted. Methods of treating plant growth media with such compounds and formulations thereof are also contemplated within this invention.


          Full Article

          ranch

          Truss and column structures incorporating natural round timbers and natural branched round timbers

          By www.freepatentsonline.com
          Published On :: Tue, 26 May 2015 08:00:00 EDT

          Trusses comprising natural round timbers as top and bottom cords are provided. Also provided are truss and column assemblies comprising natural branched round timber columns connected to a truss.


          Full Article

          ranch

          BRANCH CURRENT MONITOR WITH RECONFIGURATION

          By www.freepatentsonline.com
          Published On :: Thu, 29 Jun 2017 08:00:00 EDT

          A branch current monitor that includes reconfiguration.


          Full Article

          ranch

          FirstCry to open its boutique store pop-up model across 300 franchisee outlets

          By retail.economictimes.indiatimes.com
          Published On :: 2017-05-15T09:07:08+05:30

          The company has also built up an auto referencing system for its stores to stock inventory based on target group and purchasing power of customers in a given location.


          Full Article

          ranch

          FirstCry may acquire Mothercare franchisee rights from DLF brands

          By retail.economictimes.indiatimes.com
          Published On :: 2018-01-17T08:23:47+05:30

          Mothercare is the latest brand after Mango, Forever 21and Sephora among other global labels to change hands from DLF Brands.


          Full Article

          ranch

          Bata to add 500 more stores in next 5 years on franchise model

          By retail.economictimes.indiatimes.com
          Published On :: 2019-10-17T15:09:49+05:30

          Bata has already identified 180 such markets in smaller cities pan-India.


          Full Article

          ranch

          One of the biggest video game franchises might come to the iPhone

          By retail.economictimes.indiatimes.com
          Published On :: 2014-12-02T12:06:56+05:30

          Pokemon is the most successful and lucrative video game franchise in the world, second only to Mario.


          Full Article

          ranch

          Rovio Entertainment,owner of the Angry Birds franchise, aims to become default app on India smartphones

          By retail.economictimes.indiatimes.com
          Published On :: 2014-12-13T16:27:37+05:30

          Rovio’s India head also said that the company wants to have its own retail store where it can sell Angry Birds merchandise such as shirts and stuffed toys.


          Full Article

          ranch

          ‘Talwalkars to be Snap Fitness franchisees in 6 Asian countries outside India’

          By retail.economictimes.indiatimes.com
          Published On :: 2017-07-11T15:16:00+05:30

          The affordable gyms under Talwalkar-Snap Fitness tieup to open first in Singapore and Malaysia.


          Full Article

          ranch

          Boots 'temporarily' closes 60 branches across the UK - full list of stores

          By www.glasgowtimes.co.uk
          Published On :: Fri, 17 Apr 2020 05:00:00 +0100

          Health, beauty and pharmacy chain Boots has said it is 'temporarily closing' 60 of its branches during the UK lockdown.


          Full Article