If you can draw a line through the three points: (0,0), v, and Av
44 karma · joined August 15, 2007
The inversion of the parameters is now noticeable. You started with basically a donut with a very wide hole (formed by the pant legs -- I'm ignoring the hole where your waist goes). After the inversion, the pant legs form a donut which is very narrow (just the width of the inside of the pant leg) and is very tall (the height of the pant leg).
This is on pages 28-29 of this issue.
int putchar ( int ) ;
int main ( void )
{
int z;
int width = 9;
int height = 10;
for (z = 0; z < width * height; z++)
{
int x = z % width;
int y = z / width;
putchar (
x + y > 3 && /* top left */
x + y < 14 && /* bottom right */
y < x + 6 && /* bottom left */
y > x - 5 /* top right */
? '*' : ' ' );
if (x == width - 1)
putchar ( '\n' );
};
putchar ( '\n' ) ;
return 0;
}
The fun part is that you can now play with the various settings. Try increasing the height and width and scaling the equations appropriately. Replace x by 2 * x or x * x for more interesting shapes. You can bound the picture by any equations you like. Example: http://ideone.com/53Qh3
Right, eat less if trying to lose weight and eat more if trying to bulk up. But what if you are trying to lose fat and gain muscle?
If the conjecture is true then any finite sequence of numbers can be found in the digits of pi. As others have noted, infinite sequences are not guaranteed or even likely to appear. As zackattack points out, for example, the decimal expansion of 1/9 does not appear in the digits of pi.
"gniog ot yrt siht tuo txen keew"Regarding the push command, it currently does not allow both the --all and --tags options to be used together (very strange).
Regarding not pushing temporary branches, this seems contrary to one of the reasons I started using git: it makes branches cheap and easy to throw away when you are done with them.
I can understand the way git works regarding each developer using only the branches they are interested in, but I can't seem scale this philosophy down to a single developer. I want all my working copies to be the same. I want new branches to propagate. I want branch deletions to propagate.
I've thought about scripting some of this, but for some pieces I am not sure how to proceed. Consider branch deletion. The problem here is that I can delete the branch from the main repository, but that doesn't force deletion for each of the clients. Instead, I would need to write a custom "git pull" style command that I run in a working directory before I start my work. Should this command delete all remote branches so that actual deletions are propagated, and then "git pull" restores the remote branches which still exist?
[edit: I've discovered that "git remote prune" will delete remote tracking branches that are no longer in the repo]
Don't other git users have this issue? Presumably there are others who work from more than one location and want a consistent view from each, yet I can't seem to google for any help on these issues.
Right now, I have a main server set up where I push my changes to after finishing work for the day. But now suppose I create some new tags and branches. I need to do
git push --all
git push --tags
git pull
git checkout --track -b <new-branch> origin/<new-branch>
git branch -d <branch-name>
git push origin :<branch-name>
Does anybody know a way to simplify this workflow with git?