On Sunday, 9 September 2018 at 04:37:48 UTC, Josphe Brigmo wrote:
If git would automatically do the dates
It does.
To get changes for a whole file:
git log filename
To get changes for part of a file:
git log -L startLine,endLine filename
There are formatting options for git log to pare
On Sunday, 9 September 2018 at 01:27:06 UTC, Josphe Brigmo wrote:
This has nothing to do with git. People think git is the end
all be all. What if git is not available, then what? It's
moronic to think that one has to use one or the other when both
options are available and both only add inform
On Sunday, 9 September 2018 at 04:59:08 UTC, Josphe Brigmo wrote:
Yes, but the fact is they would not appreciate my work because
they do not appreciate it now.
I can't really argue against that logic.
But then again, I fail to see when such a situation would apply.
I personally use the tortoi
On 9/8/2018 9:37 PM, Josphe Brigmo wrote:
[...]s**t[...]
We expect professional demeanor here. Please don't use such language.
On 09/09/2018 5:43 PM, Paul Backus wrote:
On Sunday, 9 September 2018 at 04:37:48 UTC, Josphe Brigmo wrote:
If git would automatically do the dates then one could download the
source code. Git would be the central repository and if one wanted an
offline version that had enough info in it such a
On Sunday, 9 September 2018 at 04:37:48 UTC, Josphe Brigmo wrote:
If git would automatically do the dates then one could download
the source code. Git would be the central repository and if one
wanted an offline version that had enough info in it such as
the data a change was made, who changed
On Sunday, 9 September 2018 at 02:48:40 UTC, Neia Neutuladh wrote:
On Sunday, 9 September 2018 at 01:27:06 UTC, Josphe Brigmo
wrote:
How hard would it be to automate dating for dmd source so that
everything is consistent in a way that makes sense?
Perhaps you could find out by trying to implem
On Sunday, 9 September 2018 at 02:49:45 UTC, Walter Bright wrote:
On 9/8/2018 4:29 AM, Josphe Brigmo wrote:
Um, I didn't say don't use Git!
I've done this manually before git. I can guarantee you that
the dates put in the file are invariably wrong, incomplete, or
non-existent.
But if you b
On Sunday, 9 September 2018 at 01:27:06 UTC, Josphe Brigmo wrote:
How hard would it be to automate dating for dmd source so that
everything is consistent in a way that makes sense?
Perhaps you could find out by trying to implement such a system?
That's what I usually do.
You haven't describe
On 9/8/2018 4:29 AM, Josphe Brigmo wrote:
Um, I didn't say don't use Git!
I've done this manually before git. I can guarantee you that the dates put in
the file are invariably wrong, incomplete, or non-existent.
But if you bring up a source file in github, and click on the "Blame" button,
i
On Saturday, 8 September 2018 at 18:47:39 UTC, Neia Neutuladh
wrote:
On Saturday, 8 September 2018 at 06:59:28 UTC, Josphe Brigmo
wrote:
Having source code that doesn't show changes with dates is
pretty useless for diagnostics. I realize that git has the
changes but the source code should.
Wh
On Saturday, 8 September 2018 at 06:59:28 UTC, Josphe Brigmo
wrote:
Having source code that doesn't show changes with dates is
pretty useless for diagnostics. I realize that git has the
changes but the source code should.
What problem did you encounter where you had trouble getting the
inform
On Saturday, 8 September 2018 at 07:08:46 UTC, Colin wrote:
Some ad hoc comment system in source code to point out changes
will never be as good.
Just Use Git!
I'd agree for implementation changes, but *interface* changes
should be not just in the comment, but in a doc comment. Ddoc
specifi
On Saturday, September 8, 2018 6:35:32 AM MDT tide via Digitalmars-d wrote:
> Dates won't help, if you have a comment with a date that states
> everything under it was modified at that date. What happens when
> there's a split of 3-4 lines between modifications? Just how many
> of these comments ar
On Saturday, 8 September 2018 at 12:36:01 UTC, Paul Backus wrote:
On Saturday, 8 September 2018 at 11:29:15 UTC, Josphe Brigmo
wrote:
Um, I didn't say don't use Git!
Your illogic is that you believe that one can have only one or
the other when one can have both. Hence, you are excluding a
com
On Saturday, 8 September 2018 at 11:29:15 UTC, Josphe Brigmo
wrote:
Um, I didn't say don't use Git!
Your illogic is that you believe that one can have only one or
the other when one can have both. Hence, you are excluding a
completely valid addition. You think it is an alternative. You
are wr
On Saturday, 8 September 2018 at 11:29:15 UTC, Josphe Brigmo
wrote:
On Saturday, 8 September 2018 at 07:08:46 UTC, Colin wrote:
On Saturday, 8 September 2018 at 06:59:28 UTC, Josphe Brigmo
wrote:
Having source code that doesn't show changes with dates is
pretty useless for diagnostics. I realiz
On Saturday, 8 September 2018 at 11:29:15 UTC, Josphe Brigmo
wrote:
On Saturday, 8 September 2018 at 07:08:46 UTC, Colin wrote:
On Saturday, 8 September 2018 at 06:59:28 UTC, Josphe Brigmo
wrote:
Having source code that doesn't show changes with dates is
pretty useless for diagnostics. I realiz
On Saturday, 8 September 2018 at 07:08:46 UTC, Colin wrote:
On Saturday, 8 September 2018 at 06:59:28 UTC, Josphe Brigmo
wrote:
Having source code that doesn't show changes with dates is
pretty useless for diagnostics. I realize that git has the
changes but the source code should.
If some cod
On Saturday, 8 September 2018 at 06:59:28 UTC, Josphe Brigmo
wrote:
Having source code that doesn't show changes with dates is
pretty useless for diagnostics. I realize that git has the
changes but the source code should.
If some code is added or changed it is very simple to add the
date of c
Having source code that doesn't show changes with dates is pretty
useless for diagnostics. I realize that git has the changes but
the source code should.
If some code is added or changed it is very simple to add the
date of change in a comment.
// Date: Date1, Date2, Date3,
Anything be
21 matches
Mail list logo
