On Wed, Aug 28, 2013 at 04:18:03PM -0400, Jeff King wrote:
> On Wed, Aug 28, 2013 at 01:05:38PM -0700, Junio C Hamano wrote:
>
> > What are our plans to help existing scripts people have written over
> > time, especially before "status -s" was invented, that will be
> > broken by use of this?
>
>
David Aguilar writes:
> I have a poor imagination and cannot imagine why it needs to be
> switchable.
I could not either, but I found the reason in the commit message:
eff80a9fd990
Some users do want to write a line that begin with a pound sign, #,
in their commit log message. Many tra
Jonathan Nieder writes:
> Matthieu Moy wrote:
>
>>In the long run, if users
>> like the non-prefix output, it may make sense to flip the default value
>> to true.
>
> Hmm, do you mean that the configuration is to give the change-averse
> some time t
Matthieu Moy wrote:
> Historically, "git status" needed to prefix each output line with '#' so
> that the output could be added as comment to the commit message. This
> prefix comment has no real purpose when "git status" is ran from the
> command-line, and this may distract users from the real co
David Aguilar writes:
> On Wed, Aug 28, 2013 at 2:39 PM, Junio C Hamano wrote:
>> Jeff King writes:
>>
>>> On Wed, Aug 28, 2013 at 01:05:38PM -0700, Junio C Hamano wrote:
>>>
What are our plans to help existing scripts people have written over
time, especially before "status -s" was i
On Wed, Aug 28, 2013 at 2:39 PM, Junio C Hamano wrote:
> Jeff King writes:
>
>> On Wed, Aug 28, 2013 at 01:05:38PM -0700, Junio C Hamano wrote:
>>
>>> What are our plans to help existing scripts people have written over
>>> time, especially before "status -s" was invented, that will be
>>> broken
Matthieu Moy writes:
> Junio C Hamano writes:
>
>> Matthieu Moy writes:
>>
>>> diff --git a/Documentation/config.txt b/Documentation/config.txt
>>> index ec57a15..dacf4b9 100644
>>> --- a/Documentation/config.txt
>>> +++ b/Documentation/config.txt
>>> @@ -2118,6 +2118,11 @@ status.branch::
>>>
Matthieu Moy writes:
> diff --git a/wt-status.c b/wt-status.c
> index cb24f1f..97068d5 100644
> --- a/wt-status.c
> +++ b/wt-status.c
> @@ -774,12 +778,21 @@ static void wt_status_print_tracking(struct wt_status
> *s)
> if (!format_tracking_info(branch, &sb))
> return;
>
>
Jeff King writes:
> On Wed, Aug 28, 2013 at 01:05:38PM -0700, Junio C Hamano wrote:
>
>> What are our plans to help existing scripts people have written over
>> time, especially before "status -s" was invented, that will be
>> broken by use of this?
>
> I thought that our response to parsing the
Junio C Hamano writes:
> Matthieu Moy writes:
>
>> diff --git a/Documentation/config.txt b/Documentation/config.txt
>> index ec57a15..dacf4b9 100644
>> --- a/Documentation/config.txt
>> +++ b/Documentation/config.txt
>> @@ -2118,6 +2118,11 @@ status.branch::
>> Set to true to enable --branc
On Wed, Aug 28, 2013 at 01:05:38PM -0700, Junio C Hamano wrote:
> What are our plans to help existing scripts people have written over
> time, especially before "status -s" was invented, that will be
> broken by use of this?
I thought that our response to parsing the long output of "git status"
w
Junio C Hamano writes:
> "status.omitCommentPrefix" that defaults to false might be a better
> setting, I suspect.
Or status.showCommentPrefix that defaults to true; I didn't mean to
say a setting that defaults to false is preferred over one that
defaults to true in my message.
--
To unsubscribe
Matthieu Moy writes:
> diff --git a/Documentation/config.txt b/Documentation/config.txt
> index ec57a15..dacf4b9 100644
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -2118,6 +2118,11 @@ status.branch::
> Set to true to enable --branch by default in linkgit:git-statu
Historically, "git status" needed to prefix each output line with '#' so
that the output could be added as comment to the commit message. This
prefix comment has no real purpose when "git status" is ran from the
command-line, and this may distract users from the real content.
Allow the user to dis
14 matches
Mail list logo
