All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <ltuikov@yahoo.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: New way of tracking remote branches -- question
Date: Tue, 9 Jan 2007 00:41:30 -0800 (PST)	[thread overview]
Message-ID: <181306.34035.qm@web31814.mail.mud.yahoo.com> (raw)
In-Reply-To: <7vejq4r4ci.fsf@assigned-by-dhcp.cox.net>

--- Junio C Hamano <junkio@cox.net> wrote:
> > I guess, what I want is still to be able to "see" remotes/
> > when I do "git branch".
> 
> Then do not use "remotes/" but hang everything underneath
> "heads/" (or "git branch -a").
> 
> Of course, the next complaint from you would be that the latest
> git-clone would not make the traditional layout, but ...

What I meant was something of the lines of "git branch -r".
As I said, I don't mind the new way of seprating remote
branches per repo as is done by remotes/*/ .

> We've taken "one step at a time" by first introducing separate
> remote layout as an option, taught 'git branch' the needed
> options such as -a and -r, and then made this the default
> layout.  It still looks _different_ to me from what I am used
> to, but that's just traditionalist speaking and I cannot really
> deny the advantage of the separate remote layout offers.  In
> other words, we have been doing "one step at a time".

Me neither.  I also think there is an advantage of separately
tracking remotes as per remotes/*/ , so that organization is
better, i.e. per remote repo.

    Luben

  reply	other threads:[~2007-01-09  8:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05 23:02 New way of tracking remote branches -- question Luben Tuikov
2007-01-05 23:17 ` Junio C Hamano
2007-01-05 23:39   ` Junio C Hamano
2007-01-06  0:39     ` Luben Tuikov
2007-01-06  0:16   ` Luben Tuikov
2007-01-05 23:50 ` Junio C Hamano
2007-01-06  1:11   ` Junio C Hamano
2007-01-06  2:11     ` Steven Grimm
2007-01-06 14:10     ` Theodore Tso
2007-01-09  7:45     ` Luben Tuikov
2007-01-09  8:28       ` Junio C Hamano
2007-01-09  8:41         ` Luben Tuikov [this message]
2007-01-09  8:57   ` Martin Langhoff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=181306.34035.qm@web31814.mail.mud.yahoo.com \
    --to=ltuikov@yahoo.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.