Mahmoud Al-Qudsi writes:
> Looking back, I probably should have started with that. `git
> status` gives the status of the _relative_ current state of the
> local repository without printing any information that can be used
> as an _absolute_ reference to "frame" the results of the `git
> status`
On Fri, Jun 16, 2017 at 4:41 PM, Junio C Hamano wrote:
>
> HEAD is, unless you are about to create a root commit, always a
> commit and not other kind of commit-ish, so there is no need to say
> "or commit-ish" here.
I apologize for my errant terminology, I thought commitish was what
the abbrevia
Mahmoud Al-Qudsi writes:
> I hope it is not considered too forward of me for my first post to this list
> to be a suggestion on a change to git’s behavior (though not in any
> functional manner); but a persistent frustration for me and everyone I’ve
> worked with (so, yes, 100% based off of anecd
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
On Thu, Jun 15, 2017 at 7:43 PM, Mahmoud Al-Qudsi wrote:
> Hello all,
>
> I hope it is not considered too forward of me for my first post to this list
> to be a suggestion on a change to git’s behavior (though not in any
> functional manner); but a persistent frustration for me and everyone I’ve
>
Hello all,
I hope it is not considered too forward of me for my first post to this list
to be a suggestion on a change to git’s behavior (though not in any
functional manner); but a persistent frustration for me and everyone I’ve
worked with (so, yes, 100% based off of anecdata) has been that the
6 matches
Mail list logo
