Re: feature request: user email config per domain

2017-02-22 Thread Igor Djordjevic BugA
Hi Tushar, On 22/02/2017 14:12, Tushar Kapila wrote: > So when remote URL has github.com push as tgkp...@search.com but for > testing.abc.doman:8080 use tgkp...@test.xyz.com ? I`m not sure if this is sensible, as authorship information is baked into the commit at the time of committing, which (u

Re: [git-gui] Amending doesn't preserve timestamp

2017-02-12 Thread Igor Djordjevic BugA
On 12/02/2017 22:40, Juraj wrote: > Hi Igor, > > I forgot to write the version I'm using. It's on Ubuntu 16.04, git-gui > package version 1:2.7.4-0ubuntu1 (--version: git-gui version 0.20.0), > git version 2.7.4, tcl and tk 8.6.0+9. Perhaps it got fixed in a newer > version, in that case, my bad f

Re: [git-gui] Amending doesn't preserve timestamp

2017-02-12 Thread Igor Djordjevic BugA
On 12/02/2017 21:50, Juraj wrote: > I've just noticed that amending a commit from git-gui uses the time of > amending as the new timestamp of the commit, whereas git commit > --amend preserves the original timestamp. Maybe the two should work > the same, whatever it is decided to be the standard be

Re: git-apply: warn/fail on *changed* end of line (eol) *only*?

2016-12-27 Thread Igor Djordjevic BugA
On 27/12/2016 18:27, Junio C Hamano wrote: > To see the problem with "check existing lines", it probably is > easier to extend the above example to start from a file with one > more line, like this: > > 1 > 3 > 4 > 5 > > and extend all the example patches to remove "4 " line as

Re: git-apply: warn/fail on *changed* end of line (eol) *only*?

2016-12-26 Thread Igor Djordjevic BugA
Hi Junio, and thanks for sharing your thoughts. You understood it pretty well, except the context "scope". Example does show a single line change, and a single line old/new comparison, but that is for simplicity sake of the initial example. What I was discussing about was the whole patch "hunk" in

Re: git-apply: warn/fail on *changed* end of line (eol) *only*?

2016-12-25 Thread Igor Djordjevic BugA
On 26/12/2016 00:49, Igor Djordjevic BugA wrote: > This is a follow-up of a message posted at git-users Google group[1], > as the topic may actually be better suited for this mailing list > instead. If needed, some elaboration on the context can be found there, > as well as a deta

git-apply: warn/fail on *changed* end of line (eol) *only*?

2016-12-25 Thread Igor Djordjevic BugA
Hi to all, This is a follow-up of a message posted at git-users Google group[1], as the topic may actually be better suited for this mailing list instead. If needed, some elaboration on the context can be found there, as well as a detailed example describing the motive for the question itself (or