"brian m. carlson" writes:
> The hash of the source file isn't generally as much of a problem,
> because the patch tends to change, even incidentally (line numbers and
> such), when the hash of the file changes. It's also something that we
> have in our history, whereas the temporary branch we r
On Sun, Dec 06, 2015 at 06:49:14PM -0800, Junio C Hamano wrote:
> "brian m. carlson" writes:
>
> > git format-patch is often used to create patches that are then stored in
> > version control or displayed with diff. Having the commit hash in the
> > "From " line usually just creates diff noise i
"brian m. carlson" writes:
> git format-patch is often used to create patches that are then stored in
> version control or displayed with diff. Having the commit hash in the
> "From " line usually just creates diff noise in these cases, so this
> series introduces --no-hash to set that to all ze
git format-patch is often used to create patches that are then stored in
version control or displayed with diff. Having the commit hash in the
"From " line usually just creates diff noise in these cases, so this
series introduces --no-hash to set that to all zeros.
The idea for this series came f
4 matches
Mail list logo
