All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Paolo Bonzini <bonzini@gnu.org>,
	git@vger.kernel.org, Daniel Barkalow <barkalow@iabervon.org>
Subject: Re: [PATCH] branch --track: code cleanup and saner handling of local branches
Date: Mon, 09 Jul 2007 15:01:25 -0700	[thread overview]
Message-ID: <7vzm25tex6.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0707092203100.5546@racer.site> (Johannes Schindelin's message of "Mon, 9 Jul 2007 22:05:14 +0100 (BST)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

>> It strikes me a bit odd if Daniel's remote.[ch] infrastructure
>> does not give you easy access to this kind of information...
>
> Yes, probably.  However, at the time he was sending that patch, I was 
> already preparing the patch.

I was talking about existing remote.[ch] patches, which has been
in tree since late May this year, not his recent round of
"approach to builtin git-fetch" series.

  reply	other threads:[~2007-07-09 22:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 21:54 [RFC/PATCH] git-branch: default to --track Johannes Schindelin
2007-07-08  8:59 ` Junio C Hamano
2007-07-08 12:41   ` [PATCH] branch.autosetupmerge: allow boolean values, or "all" Johannes Schindelin
2007-07-08 18:41     ` Junio C Hamano
2007-07-08 19:15       ` Johannes Schindelin
2007-07-09  1:59       ` Paolo Bonzini
2007-07-09  2:27         ` Junio C Hamano
2007-07-09 11:35           ` [PATCH] branch --track: code cleanup and saner handling of local branches Johannes Schindelin
2007-07-09 21:05             ` Junio C Hamano
2007-07-09 21:05               ` Johannes Schindelin
2007-07-09 22:01                 ` Junio C Hamano [this message]
2007-07-10  3:02                   ` [PATCH 1/2] Add for_each_remote() function, and extend remote_find_tracking() Johannes Schindelin
2007-07-10  3:55                     ` Daniel Barkalow
2007-07-10 14:11                       ` Johannes Schindelin
2007-07-10  5:07                     ` Junio C Hamano
2007-07-10  5:23                       ` Daniel Barkalow
2007-07-10 17:48                       ` [PATCH v2 " Johannes Schindelin
2007-07-10 18:38                         ` Junio C Hamano
2007-07-10 19:28                           ` Johannes Schindelin
2007-07-10 21:09                           ` Daniel Barkalow
2007-07-10 17:50                       ` [PATCH v2 2/2] branch --track: code cleanup and saner handling of local branches Johannes Schindelin
2007-07-10  3:05                   ` [PATCH " Johannes Schindelin
2007-07-09 11:28         ` [PATCH] branch.autosetupmerge: allow boolean values, or "all" Johannes Schindelin

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=7vzm25tex6.fsf@assigned-by-dhcp.cox.net \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=barkalow@iabervon.org \
    --cc=bonzini@gnu.org \
    --cc=git@vger.kernel.org \
    /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.