Re: Warning about conflict markers - undocumented 'diff --check' feature & suggestion

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ori Avtalion <ori@xxxxxxxxxxxxx> writes:

> If my change introduces a few words that exceed asciidoc's ~72-char line width,
> should I reformat the entire paragraph? (thus making it had to identify what
> changed exactly)

You should try to minimize the damage, but shouldn't go overboard ;-)

> Any thoughts on adding similar functionality to "git add"?

I am not sure what "similar functionality" you are imagining.

"git add" does not show any changes, it just does what it was told
to do.  If the user is unsure, s/he should make it the habit to
check what s/he is doing with "git diff".


--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]