git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Paolo Bonzini <bonzini@gnu.org>,
	git@vger.kernel.org, Daniel Barkalow <barkalow@iabervon.org>
Subject: Re: [PATCH v2 1/2] Add for_each_remote() function, and extend remote_find_tracking()
Date: Tue, 10 Jul 2007 20:28:58 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707102026010.4047@racer.site> (raw)
In-Reply-To: <7vtzscqf2r.fsf@assigned-by-dhcp.cox.net>

Hi,

On Tue, 10 Jul 2007, Junio C Hamano wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > The function for_each_remote() does exactly what the name suggests.
> >
> > The function remote_find_tracking() was extended to be able to search
> > remote refs for a given local ref.  You have to set the parameter
> > "reverse" to true for that behavior.
> 
> The updated patch does not use "reverse" but the old description
> is still there.

Urgh. Right. May I ask you to paste this instead?

The function remote_find_tracking() was extended to be able to search 
remote refs for a given local ref.  You have to set either src or dst in 
the refspec, and remote_find_tracking() will fill in the other and return 
0.

> Daniel, one thing I fear about your "I want to store the message
> in the object store so that I can reuse even after I re-polish
> the series" desire on the cover letter topic is this kind of
> gotcha, and that is why I suggested "*** BLURB GOES HERE ***".

I am happy that my fsckup served a purpose, then.  (And maybe this would 
be a good hint in rebase -i's man page, too, since that is how the error 
was introduced here.)

Ciao,
Dscho

  reply	other threads:[~2007-07-10 19:36 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
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 [this message]
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=Pine.LNX.4.64.0707102026010.4047@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=barkalow@iabervon.org \
    --cc=bonzini@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).