Branch: refs/heads/dmd-1.x
  Home:   https://github.com/D-Programming-Language/dmd
  Commit: dbd904eb3e1a9e2f8cb2e4643695a677f8fe7ea1
      https://github.com/D-Programming-Language/dmd/commit/dbd904eb3e1a9e2f8cb2e4643695a677f8fe7ea1
  Author: Walter Bright <walter@walterbright.com>
  Date:   2012-07-12 (Thu, 12 Jul 2012)

  Changed paths:
    M src/backend/elfobj.c

  Log Message:
  -----------
  durn, forgot elfobj

On Thursday, July 12, 2012 11:51:44 GitHub wrote:
> durn, forgot elfobj

I don't know exactly what your process is in terms of how you manage adding files and how you use git and whatnot, but if you run

git status

it will tell you which files have been changed and which have not been added. So, unless you routinely have files sitting in your local repository which aren't supposed to be added (and which don't make sense to put in .gitignore for whatever reason), you can use git status to easily check for files that haven't been added or committed and make sure that you don't miss any files whenever you commit. Then it will be much harder to push anything to github which won't build properly due to missing files or missing updates.

- Jonathan M Davis
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

On 12 jul 2012, at 21:01, Jonathan M Davis wrote:

> On Thursday, July 12, 2012 11:51:44 GitHub wrote:
>> durn, forgot elfobj
> 
> I don't know exactly what your process is in terms of how you manage adding files and how you use git and whatnot, but if you run
> 
> git status
> 
> it will tell you which files have been changed and which have not been added. So, unless you routinely have files sitting in your local repository which aren't supposed to be added (and which don't make sense to put in .gitignore for whatever reason), you can use git status to easily check for files that haven't been added or committed and make sure that you don't miss any files whenever you commit. Then it will be much harder to push anything to github which won't build properly due to missing files or missing updates.


I agree, I constantly use "git status" and "git diff".

.git/info/exclude is used for ignoring private files that shouldn't be put into .gitignore.

Putting this in the git config (~/.gitconfig) :

[color]
    status = auto

Will show modified and untracked files in red when using "git status". It will show files added to the index in green. It's also possible to add colors to the "diff" and "branch" commands:

[color]
    diff = auto
    branch = auto

Remote branches will show up in red and local will show up in green.

-- 
/Jacob Carlborg

_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

On 12 July 2012 21:01, Jonathan M Davis <jmdavisProg@gmx.com> wrote:
> On Thursday, July 12, 2012 11:51:44 GitHub wrote:
>> durn, forgot elfobj
>
> I don't know exactly what your process is in terms of how you manage adding files and how you use git and whatnot, but if you run
>
> git status
>
> it will tell you which files have been changed and which have not been added. So, unless you routinely have files sitting in your local repository which aren't supposed to be added (and which don't make sense to put in .gitignore for whatever reason),

Well I have that situation 100% of the time, and I bet Walter does too.
Working on the compiler is currently impossible without modifying the
makefile, largely thanks to some pedant who insisted that 'make'
should make a release build.
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

On 13 Jul 2012, at 10:33, Don Clugston wrote:
> Well I have that situation 100% of the time, and I bet Walter does too. Working on the compiler is currently impossible without modifying the makefile, largely thanks to some pedant who insisted that 'make' should make a release build.

Then just add a debug target to the makefile, and problem solved?

David
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

On Jul 13, 2012, at 4:33 AM, Don Clugston <dclugston@gmail.com> wrote:

> On 12 July 2012 21:01, Jonathan M Davis <jmdavisProg@gmx.com> wrote:
>> On Thursday, July 12, 2012 11:51:44 GitHub wrote:
>>> durn, forgot elfobj
>> 
>> I don't know exactly what your process is in terms of how you manage adding files and how you use git and whatnot, but if you run
>> 
>> git status
>> 
>> it will tell you which files have been changed and which have not been added. So, unless you routinely have files sitting in your local repository which aren't supposed to be added (and which don't make sense to put in .gitignore for whatever reason),
> 
> Well I have that situation 100% of the time, and I bet Walter does too. Working on the compiler is currently impossible without modifying the makefile, largely thanks to some pedant who insisted that 'make' should make a release build.

There are several options for this. The best one is probably making an extra makefile. Gnu make has a well documented order of files it searches to find the default makefile. You can hijack make by defining a higher priority make file and put development targets in there. Ideally that'd be done by calling make on the other makefile. You can then add your customized makefile to .gitignore. You can also add .gitignore to .gitignore
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

On Jul 13, 2012, at 02:27 PM, Jason House <jason.james.house@gmail.com> wrote:

> On Jul 13, 2012, at 4:33 AM, Don Clugston <dclugston@gmail.com> wrote:
>
> > On 12 July 2012 21:01, Jonathan M Davis <jmdavisProg@gmx.com> wrote:
> >> On Thursday, July 12, 2012 11:51:44 GitHub wrote:
> >>> durn, forgot elfobj
> >>
> >> I don't know exactly what your process is in terms of how you manage adding files and how you use git and whatnot, but if you run
> >>
> >> git status
> >>
> >> it will tell you which files have been changed and which have not been added. So, unless you routinely have files sitting in your local repository which aren't supposed to be added (and which don't make sense to put in .gitignore for whatever reason),
> >
> > Well I have that situation 100% of the time, and I bet Walter does too. Working on the compiler is currently impossible without modifying the makefile, largely thanks to some pedant who insisted that 'make' should make a release build.
>
> There are several options for this. The best one is probably making an extra makefile. Gnu make has a well documented order of files it searches to find the default makefile. You can hijack make by defining a higher priority make file and put development targets in there. Ideally that'd be done by calling make on the other makefile. You can then add your customized makefile to .gitignore. You can also add .gitignore to .gitignore

<project>/.git/info/exclude is used for ignoring files that shouldn't be put into .gitignore.

--
/Jacob Carlborg

Jonathan M Davis, el 12 de July a las 15:01 me escribiste:
> On Thursday, July 12, 2012 11:51:44 GitHub wrote:
> > durn, forgot elfobj
>
> I don't know exactly what your process is in terms of how you manage adding files and how you use git and whatnot, but if you run
>
> git status

If you use Linux (or bash), you can have that information right in your prompt, I've given this tip before: http://permalink.gmane.org/gmane.comp.lang.d.dmd.devel/4302

Is extremely useful.

--
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
If you don't know what direction you should take
You don't know where you are
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

Jacob Carlborg, el 12 de July a las 21:21 me escribiste:
> I agree, I constantly use "git status" and "git diff".
>
> .git/info/exclude is used for ignoring private files that shouldn't be put into .gitignore.
>
> Putting this in the git config (~/.gitconfig) :
>
> [color]
>     status = auto
>
> Will show modified and untracked files in red when using "git status". It will show files added to the index in green. It's also possible to add colors to the "diff" and "branch" commands:
>
> [color]
>     diff = auto
>     branch = auto
>
> Remote branches will show up in red and local will show up in green.

Even better: git config --global color.ui auto (to activate colors in all the commands, avoid messing with .gitconfig manually).

--
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
Geckos can stick to any surface, with the exception of Teflon, which was
specifically engineered to prevent even van der Waals adhesion.
	-- "Research into Gecko Adhesion", Berkeley, 2007-10-14
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals

Don Clugston, el 13 de July a las 10:33 me escribiste:
> On 12 July 2012 21:01, Jonathan M Davis <jmdavisProg@gmx.com> wrote:
> > On Thursday, July 12, 2012 11:51:44 GitHub wrote:
> >> durn, forgot elfobj
> >
> > I don't know exactly what your process is in terms of how you manage adding files and how you use git and whatnot, but if you run
> >
> > git status
> >
> > it will tell you which files have been changed and which have not been added. So, unless you routinely have files sitting in your local repository which aren't supposed to be added (and which don't make sense to put in .gitignore for whatever reason),
>
> Well I have that situation 100% of the time, and I bet Walter does too. Working on the compiler is currently impossible without modifying the makefile, largely thanks to some pedant who insisted that 'make' should make a release build.

You can always separate configuration stuff in another makefile. I used that trick before and it works pretty well. Just add something like:

-include config.mak

just after any variable you want to override in the main makefile(s) (the "-" is important, makes the inclusion optional so make doesn't fail if the file is not present). Then add config.mak to .gitignore and anyone can create this config.mak to override options.

For example:
Makefile:
SOME_VAR := x
-include config.mak
x:
	make_x $SOME_VAR

make x will produce make_x x. If you create a config.mak with:
SOME_VAR := y
make x will produce make_x y


--
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
Vaporeso, al verse enfundado por la depresión, decide dar fin a su vida
tomando Chinato Garda mezclado con kerosene al 50%. Ante el duro trance
pierde la movilidad en sus miembros derechos: inferior y superior. En
ese momento es considerado como el hombre líder del movimiento de
izquierda de Occidente.
_______________________________________________
dmd-internals mailing list
dmd-internals@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-internals