> Glad to hear it was useful! I've updated the post on the blog.
It was really helpful. Thank you for updating it.
_
Racket Developers list:
http://lists.racket-lang.org/dev
> I was following your blog too, haha.
Glad to hear it was useful! I've updated the post on the blog.
_
Racket Developers list:
http://lists.racket-lang.org/dev
I was following your blog too, haha.
2012/12/14 Joe Gibbs Politz
> > Unfortunately I don't have his email, so I hope he'll read this or
> > perhaps someone here can forward this to him.
>
> Got it, I'll add to the post this evening.
> _
> Racket Developers list:
> htt
> Unfortunately I don't have his email, so I hope he'll read this or
> perhaps someone here can forward this to him.
Got it, I'll add to the post this evening.
_
Racket Developers list:
http://lists.racket-lang.org/dev
On 2012-12-13 15:34:04 -0500, Greg Hendershott wrote:
> I had a similar confusion a week ago, building Racket for the first
> time ever, and got an answer on #racket.
One thing that makes this easier is if you use the `plt-fresh-build`
script from this git repo:
https://github.com/takikawa/racke
>> I suggest building in a build/ directory as described in src/README. There's
>> already a .gitignore directive to ignore that directory.
I had a similar confusion a week ago, building Racket for the first
time ever, and got an answer on #racket.
I was following Joe Gibbs Politz's recent Racke
On Dec 13, 2012, at 6:37 AM, David Van Horn wrote:
> On 12/13/12 9:22 AM, Chen Xiao wrote:
>> I fork the codebase on my local computer. Then I .configure & make &
>> make install, as a result, there are many compiled things like bin or
>> *.o files.
>>
>> To avoid add them to my commit, I modify
On Dec 13, 2012 9:22 AM, "Chen Xiao" wrote:
>
> I fork the codebase on my local computer. Then I .configure & make & make
install, as a result, there are many compiled things like bin or *.o files.
>
> To avoid add them to my commit, I modify .gitignore to ignore them all.
Add your local ignores
If you are doing a git status and only wish to see changes applicable to
tracked files:
$ git status -uno -- .
If you are a Linux commandline type of guy, I like doing commit work using
'tig'.
On Thu, Dec 13, 2012 at 9:46 AM, Tobias Hammer wrote:
> Edit .gitgnore and then use
> git update-i
Edit .gitgnore and then use
git update-index --assume-unchanged .gitignore
to tell git to ignore the changes.
Revert with
git update-index --no-assume-unchanged .gitignore
if needed.
Tobias
On Thu, 13 Dec 2012 15:22:29 +0100, Chen Xiao
wrote:
I fork the codebase on my local computer
On 12/13/12 9:22 AM, Chen Xiao wrote:
I fork the codebase on my local computer. Then I .configure & make &
make install, as a result, there are many compiled things like bin or
*.o files.
To avoid add them to my commit, I modify .gitignore to ignore them all.
But I can't avoid add .gitignore at
11 matches
Mail list logo
