On 10.08.2011 11:33, Jonathan M Davis wrote:
On Wednesday, August 10, 2011 11:24:49 simendsjo wrote:
On 10.08.2011 09:36, Jonathan M Davis wrote:
On Wednesday, August 10, 2011 09:13:02 simendsjo wrote:
On 08.08.2011 15:36, simendsjo wrote:
I use absolute paths in a build script, and Ddoc uses
On Wednesday, August 10, 2011 11:24:49 simendsjo wrote:
> On 10.08.2011 09:36, Jonathan M Davis wrote:
> > On Wednesday, August 10, 2011 09:13:02 simendsjo wrote:
> >> On 08.08.2011 15:36, simendsjo wrote:
> >>> I use absolute paths in a build script, and Ddoc uses the full path
> >>> in a comment
On 10.08.2011 09:36, Jonathan M Davis wrote:
On Wednesday, August 10, 2011 09:13:02 simendsjo wrote:
On 08.08.2011 15:36, simendsjo wrote:
I use absolute paths in a build script, and Ddoc uses the full path in a
comment in the generated files. This makes version control very
difficult as all de
On Wednesday, August 10, 2011 09:13:02 simendsjo wrote:
> On 08.08.2011 15:36, simendsjo wrote:
> > I use absolute paths in a build script, and Ddoc uses the full path in a
> > comment in the generated files. This makes version control very
> > difficult as all developers has to use the same locati
On 08.08.2011 15:36, simendsjo wrote:
I use absolute paths in a build script, and Ddoc uses the full path in a
comment in the generated files. This makes version control very
difficult as all developers has to use the same location (and possibly
operating system). Is there a way to avoid this wit
I use absolute paths in a build script, and Ddoc uses the full path in a
comment in the generated files. This makes version control very
difficult as all developers has to use the same location (and possibly
operating system). Is there a way to avoid this without changing by
build script?
