Junio C Hamano gits...@pobox.com writes:
But at the same time, I feel that these redundant lines, especially
the latter one, would give the users a stronger cue than just saying
that bar is Untracked; do X to include reminds that bar will not
be included if nothing is done.
The one which
IMHO, It is alright as it is.
I have been using git for 4~ years now, and I still find very useful
those lines. They are like a git status while committing, and it's the
key to avoid accidental commits of objects or forgetting files in a
commit. Between that and that the commit message can't be
Javier Domingo javier...@gmail.com writes:
IMHO, It is alright as it is.
I have been using git for 4~ years now, and I still find very useful
those lines. They are like a git status while committing, and it's the
key to avoid accidental commits of objects or forgetting files in a
commit.
On Wed, Sep 11, 2013 at 3:24 AM, Matthieu Moy
matthieu@grenoble-inp.fr wrote:
Junio C Hamano gits...@pobox.com writes:
But at the same time, I feel that these redundant lines, especially
the latter one, would give the users a stronger cue than just saying
that bar is Untracked; do X to
That extra info doesn't occupy too much, and helps distinguish between
sections. They do also remember you the commands to use (thought after
some time using git, you may not need it).
Cheers,
Javier
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to
Matthieu Moy matthieu@grenoble-inp.fr writes:
Junio C Hamano gits...@pobox.com writes:
But at the same time, I feel that these redundant lines, especially
the latter one, would give the users a stronger cue than just saying
that bar is Untracked; do X to include reminds that bar will not
Junio C Hamano gits...@pobox.com writes:
Matthieu Moy matthieu@grenoble-inp.fr writes:
Junio C Hamano gits...@pobox.com writes:
But at the same time, I feel that these redundant lines, especially
the latter one, would give the users a stronger cue than just saying
that bar is
Hi,
I just noticed that the template COMMIT_EDITMSG was containing status
hints, and that they were not particularty helpfull _during_ a commit. I
think it would be sensible to ignore advice.statusHints and disable
hints unconditionally when writting to COMMIT_EDITMSG.
Any objection?
--
On 10/09/13 21:19, Matthieu Moy wrote:
Hi,
I just noticed that the template COMMIT_EDITMSG was containing status
hints, and that they were not particularty helpfull _during_ a commit. I
think it would be sensible to ignore advice.statusHints and disable
hints unconditionally when writting
Chris Packham judge.pack...@gmail.com writes:
On 10/09/13 21:19, Matthieu Moy wrote:
Hi,
I just noticed that the template COMMIT_EDITMSG was containing status
hints, and that they were not particularty helpfull _during_ a commit. I
think it would be sensible to ignore advice.statusHints
Matthieu Moy matthieu@grenoble-inp.fr writes:
Hi,
I just noticed that the template COMMIT_EDITMSG was containing status
hints, and that they were not particularty helpfull _during_ a commit. I
think it would be sensible to ignore advice.statusHints and disable
hints unconditionally when
Matthieu Moy wrote:
I just noticed that the template COMMIT_EDITMSG was containing status
hints, and that they were not particularty helpfull _during_ a commit. I
think it would be sensible to ignore advice.statusHints and disable
hints unconditionally when writting to COMMIT_EDITMSG.
Any
12 matches
Mail list logo
