Post reply

Name:
Email:
Subject:
Message icon:
Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Taimon
« on: July 17, 2009, 01:11:36 AM »

Quote from: plainab on July 16, 2009, 07:51:20 PM
Do I just replace 'input' with 'disable' or is there something else that I should enter?  I'd rather get it done right, than do something wrong and screw things up later...
Either delete the autocrlf line or set it to false.
You can see the effect of autocrlf if you do a fresh checkout and a `git diff' shows you that all files are modified.
Posted by: plainab
« on: July 16, 2009, 07:51:20 PM »

Quote from: Taimon on July 16, 2009, 04:13:40 AM
Quote from: plainab on July 15, 2009, 06:13:13 PM
When I set it up I told it to use unix style line endings, it seemed the least confusing of all the options.
I suggest you disable autocrlf  in the config (should be in "%GIT_DIR%/etc/gitconfig"). If you use an editor that keeps line endings as they are, you should be fine.
The first time I had just used the github website and that is probably what brought up the crlf issue.  Now that I've got a local copy, I plan on using ConTEXT do any edits/additions. I would think that it leaves the line endings as they are, but I don't really know...

I found the gifconfig file. Took a wild guess and forced it to open with ConTEXT (no extension so Windows won't automatically let me open it).  It's a basic text file, and the autoCRLF is set to input.  Do I just replace 'input' with 'disable' or is there something else that I should enter?  I'd rather get it done right, than do something wrong and screw things up later...

Posted by: Taimon
« on: July 16, 2009, 04:13:40 AM »

Quote from: plainab on July 15, 2009, 06:13:13 PM
When I set it up I told it to use unix style line endings, it seemed the least confusing of all the options.
I suggest you disable autocrlf  in the config (should be in "%GIT_DIR%/etc/gitconfig"). If you use an editor that keeps line endings as they are, you should be fine.
Posted by: Taimon
« on: July 16, 2009, 12:34:55 AM »

Well, at least for the diff you can say --ignore-space-at-eol.
Posted by: the bigg
« on: July 15, 2009, 06:39:56 PM »

cough some git guru should tell me the option to ignore crlf issues cough
Posted by: plainab
« on: July 15, 2009, 06:13:13 PM »

Finally got msysgit to work.  So now I should be able to add macros or functions to the appropriate tpp files, push the changes to my public repo and ask for them to be pulled.
When I set it up I told it to use unix style line endings, it seemed the least confusing of all the options.  Also, might solve some of the crlf issues I apparently had the last time I made some adjustments...

Posted by: the bigg
« on: July 02, 2009, 06:39:01 PM »

I received correctly the patches. The only hiccup was that you sent the whole files as patches because of CRLF issues, but this is not a git(hub) issue.
Posted by: plainab
« on: July 02, 2009, 02:38:57 PM »

I tested out github. Hope it worked. I think it did. Taimon sent me an e-mail saying that I didn't have to send requests for him to look at my edits.
But I didn't do everything that was listed in the instructions.  I just used the github website.  Is that sufficient? Or do I need to figure out how to use the various offline programs?
If it helps, the only thing I'd ever do is add new macros and/or functions and adjust the readme doc to include information about them.  I'll leave the actual "weidu engine" alone...
Posted by: Mike1072
« on: January 14, 2009, 08:20:57 PM »

Quote from: Taimon on January 14, 2009, 08:31:46 AM
Just for the record, here is what I did for to get started:
  • `git clone git://github.com/vbigiani/weidu.git'
  • log into github and fork the main project
  • `git remote add mypub git@github.com:<username>/weidu.git'

And these were the steps for the changes:
  • `git pull' for syncing the local repos with upstream (runs git fetch + git merge)
  • edit + `git commit -a'
  • `git push mypub' for pushing the changes to my public repos on github
Just wanted to say, this works and is relatively easy.

Thanks for the instructions.
Posted by: Taimon
« on: January 14, 2009, 11:04:20 AM »

Yep, the `git pull' there fetches any updates from your repos  (as this was the one I cloned from) and merges them into the current branch.
Posted by: the bigg
« on: January 14, 2009, 08:47:47 AM »

Quote from: Taimon on January 14, 2009, 08:31:46 AM
Just for the record, here is what I did for to get started:
  • `git clone git://github.com/vbigiani/weidu.git'
  • log into github and fork the main project
  • `git remote add mypub git@github.com:<username>/weidu.git'

And these were the steps for the changes:
  • `git pull' for syncing the local repos with upstream (runs git fetch + git merge)
  • edit + `git commit -a'
  • `git push mypub' for pushing the changes to my public repos on github
Um, does that sync with my repo before your editing?
Posted by: Taimon
« on: January 14, 2009, 08:31:46 AM »

Just for the record, here is what I did for to get started:
  • `git clone git://github.com/vbigiani/weidu.git'
  • log into github and fork the main project
  • `git remote add mypub git@github.com:<username>/weidu.git'

And these were the steps for the changes:
  • `git pull' for syncing the local repos with upstream (runs git fetch + git merge)
  • edit + `git commit -a'
  • `git push mypub' for pushing the changes to my public repos on github
Posted by: the bigg
« on: January 14, 2009, 07:01:44 AM »

The workflow is like this:
setup:
install cygwin, and the git and ssh package.
register at github. Follow the instructions for setting up git and ssh and providing all the required info.
Fork my github repository (via github)
Via cygwin, create a new directory (for ex. WeiDU-devel), cd into it, and run `git init && git remote add mypub git@github:<username>/weidu.git'

writing publishing one or more diffs:
via github, merge your repository with mine.
cd into the git directory
git pull mypub
do whatever change you might want and test it
git commit -a -m 'one line description of the patch'
git push mypub master

once you're done and your work is tested:
if you're a contributor: push your commit to my repository (via github)
if not: send me a pull request

I don't need either because I subscribe via RSS to everything happening to vbigiani/weidu, but a push to my repo/pull request is a good way of telling me 'I'm done with this work, and it's tested'.
Posted by: Taimon
« on: January 14, 2009, 06:06:05 AM »

The fork process is a special github action.
By clicking on the fork button you basically create your own public repository (that is somehow linked to the original project) and push your local changes into it.
(Try something like `git remote add mypub git@github.com:username/weidu.git' and then `git push mypub'.)
Posted by: Mike1072
« on: January 14, 2009, 02:19:59 AM »

I tried making some edits to the docs via Cygwin.  Hadn't used git before but I think that it worked...

However, I'm pretty lost as to whether I should be also doing stuff on the website or just via the command-line.  Also I don't know about all this branch/forking stuff.