On Mon, Oct 29, 2012 at 5:41 PM, Jeff King wrote:
> On Mon, Oct 29, 2012 at 02:05:14PM -0400, Phil Hord wrote:
>
>> I'm currently splitting this out into a series and reconsidering some
>> of it along the way. I need some guidance.
>>
>> I want to support these two modes:
>>
>> A. 'git status
On Mon, Oct 29, 2012 at 02:05:14PM -0400, Phil Hord wrote:
> I'm currently splitting this out into a series and reconsidering some
> of it along the way. I need some guidance.
>
> I want to support these two modes:
>
> A. 'git status --short' with sequence tokens added:
>## conflicte
On Thu, Oct 25, 2012 at 12:05 PM, Phil Hord wrote:
>
> Jeff King wrote:
>> On Tue, Oct 23, 2012 at 04:02:54PM -0400, Phil Hord wrote:
>>
>>> Teach git-status to report the sequencer state in short form
>>> using a new --sequencer (-S) switch. Output zero or more
>>> simple state token strings ind
Jeff King wrote:
> On Tue, Oct 23, 2012 at 04:02:54PM -0400, Phil Hord wrote:
>
>> Teach git-status to report the sequencer state in short form
>> using a new --sequencer (-S) switch. Output zero or more
>> simple state token strings indicating the deduced state of the
>> git sequencer.
>>
>> Int
On Tue, Oct 23, 2012 at 04:02:54PM -0400, Phil Hord wrote:
> Teach git-status to report the sequencer state in short form
> using a new --sequencer (-S) switch. Output zero or more
> simple state token strings indicating the deduced state of the
> git sequencer.
>
> Introduce a common function t
5 matches
Mail list logo