Duy Nguyen writes:
> On Mon, May 23, 2016 at 7:58 AM, Junio C Hamano wrote:
>> That is, I wonder if the above can become something like:
>>
>>> From github.com:pclouds/git
>>> * [new branch] { -> pclouds/}2nd-index
>>> * [new branch] { -> pclouds/}3nd-index
>>> * [new branch] {
On Mon, May 23, 2016 at 7:58 AM, Junio C Hamano wrote:
> That is, I wonder if the above can become something like:
>
>> From github.com:pclouds/git
>> * [new branch] { -> pclouds/}2nd-index
>> * [new branch] { -> pclouds/}3nd-index
>> * [new branch] { -> pclouds/}file-watcher
>>
On 2016-05-26 03:31 PM, Junio C Hamano wrote:
Marc Branchaud writes:
The fact that something is buried in some odd part of the ref tree is
less relevant, IMO. If I'm using custom fetch refspecs or other
oddities, I'll have that in the back of my head. But what I really
care about is what ref
Marc Branchaud writes:
> The fact that something is buried in some odd part of the ref tree is
> less relevant, IMO. If I'm using custom fetch refspecs or other
> oddities, I'll have that in the back of my head. But what I really
> care about is what ref I can use with commands like log and che
On 2016-05-26 01:42 PM, Junio C Hamano wrote:
True. One of the entries in Marc's example is easily misread as
"pclouds/2nd-index branch at its refs/heads/pclouds/2nd-index was
fetched to its usual place", when Marc wanted to say "they had
2nd-index branch at refs/heads/2nd-index, and it was cop
Jeff King writes:
> On Thu, May 26, 2016 at 10:22:25AM -0400, Marc Branchaud wrote:
>
>> Why do we need any kind of "->" at all? How about simply (with an update to
>> "old-branch" for comparison to probably-more-common output):
>>
>> From github.com:pclouds/git
>>cafed0c..badfeed pclouds/
On Thu, May 26, 2016 at 10:22:25AM -0400, Marc Branchaud wrote:
> Why do we need any kind of "->" at all? How about simply (with an update to
> "old-branch" for comparison to probably-more-common output):
>
> From github.com:pclouds/git
>cafed0c..badfeed pclouds/old-branch
> * [new branch]
On 2016-05-22 09:59 PM, Duy Nguyen wrote:
On Mon, May 23, 2016 at 7:58 AM, Junio C Hamano wrote:
That is, I wonder if the above can become something like:
From github.com:pclouds/git
* [new branch] { -> pclouds/}2nd-index
* [new branch] { -> pclouds/}3nd-index
* [new branch]
On Sun, May 22, 2016 at 06:20:18PM +0700, Nguyễn Thái Ngọc Duy wrote:
> To make all "->" aligned, we may need to go through the ref list
> twice, or buffer the output and let column.c align it. Either way
> needs a lot more work than this.
I don't think a two-pass approach is _too_ bad. The trick
On Mon, May 23, 2016 at 7:58 AM, Junio C Hamano wrote:
> That is, I wonder if the above can become something like:
>
>> From github.com:pclouds/git
>> * [new branch] { -> pclouds/}2nd-index
>> * [new branch] { -> pclouds/}3nd-index
>> * [new branch] { -> pclouds/}file-watcher
>>
Nguyễn Thái Ngọc Duy writes:
> Currently fetch hard-codes the "remote" column to be 10. For repos
> with long branch names, the output could look ugly like this
>
> From github.com:pclouds/git
> * [new branch] 2nd-index -> pclouds/2nd-index
> * [new branch] 3nd-index -> pclouds/3nd
Currently fetch hard-codes the "remote" column to be 10. For repos
with long branch names, the output could look ugly like this
>From github.com:pclouds/git
* [new branch] 2nd-index -> pclouds/2nd-index
* [new branch] 3nd-index -> pclouds/3nd-index
* [new branch] file-watcher -
12 matches
Mail list logo
