Extending `git pull` to deal with unindexed changes that would be overwritten

ready does what's requested that I just don't know about -- in which case, please do enlighten me! Thank you for your consideration, Mahmoud Al-Qudsi NeoSmart Technologies

Shouldn't git be able to apply diffs that it created with --ignore-whitespace?

are.neosmart.net/View/Index/nGujqm.diff * http://share.neosmart.net/View/Index/f4dkVF.diff (You can download them as-is by clicking the floppy icon in the top-right) With thanks, Mahmoud Al-Qudsi NeoSmart Technologies

Re: [PATCH] Makefile: make NO_ICONV really mean "no iconv"

t; Makefile to add "-liconv" to the linker flags. config.mak.uname > automatically defines NEEDS_LIBICONV for platforms which require it. > The adding of "-liconv" is done unconditionally, despite NO_ICONV. > > Work around this problem by making NO_ICONV take precedence

Is NO_ICONV misnamed or is it broken?

efined (i.e. it does not remove the dependency on libiconv) or is this a bug and iconv should not, in fact, be required? Many thanks, Mahmoud Al-Qudsi NeoSmart Technologies

(Some?) control codes not escaped when using `git add -p`

everyone else feels about that (or if it's already used elsewhere). Anyway, I'm sure I'm not the only one to run into this. Seeking options and interested in the various viewpoints on how this should be correctly handled (or explanations for why it's already correct as-is). Cheers, Mahmoud Al-Qudsi NeoSmart Technologies

Suggestion: better error message when an ambiguous checkout is executed

solved > xxx can refer to one of the following: > * branch origin1/xxx > * branch origin2/xxx or, less ideally but much simpler, only the first line of that message? Thank you, Mahmoud Al-Qudsi NeoSmart Technologies

Re: [suggestion] Include commit-ish in git status output

liar with git knows that the output of `git status` is only showing you a summary of the diff of the working tree vs HEAD. My argument is that all it would take is another 8 characters appending to the "On branch xxxx" line to make it an infinitely more useful command. Thank you, Mahmoud Al-Qudsi NeoSmart Technologies

Re: [suggestion] Include commit-ish in git status output

On Thu, Jun 15, 2017 at 6:55 PM, Samuel Lijin wrote: > > Can you elaborate on why you consider this useful specifically? Personally, primary usages of the current commit-ish info are to file bug reports that include the specific git revision of any given branch that a bug was observed in/on and t

[suggestion] Include commit-ish in git status output

matches. Additionally, if this list is not the right place to make such a suggestion, then I would appreciate if someone could kindly point me in the correct direction and apologize for littering. Thank you kindly, Mahmoud Al-Qudsi NeoSmart Technologies