From: Shawn Pearce <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Allow non-fast-forward of remote tracking branches in default clone
Date: Thu, 28 Dec 2006 23:35:25 -0500 [thread overview]
Message-ID: <20061229043525.GC12072@spearce.org> (raw)
In-Reply-To: <7vk60btucu.fsf_-_@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> This changes the default remote.origin.fetch configuration
> created by git-clone so that it allows non-fast-forward updates.
Ack'd, but only if '[PATCH 1/2] core.logallrefupdates: log remotes/
tracking branches.' is also applied.
I think both are worth applying.
--
Shawn.
next prev parent reply other threads:[~2006-12-29 4:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 20:31 branch.pu.forcefetch Pavel Roskin
2006-12-27 21:14 ` branch.pu.forcefetch Jakub Narebski
2006-12-27 21:14 ` branch.pu.forcefetch Junio C Hamano
2006-12-27 21:20 ` branch.pu.forcefetch Jakub Narebski
2006-12-28 21:29 ` branch.pu.forcefetch Pavel Roskin
2006-12-28 22:44 ` branch.pu.forcefetch Junio C Hamano
2006-12-29 0:32 ` [PATCH 1/2] core.logallrefupdates: log remotes/ tracking branches Junio C Hamano
2006-12-29 0:32 ` [PATCH 2/2] Allow non-fast-forward of remote tracking branches in default clone Junio C Hamano
2006-12-29 4:35 ` Shawn Pearce [this message]
2006-12-29 16:39 ` Johannes Schindelin
2006-12-29 1:22 ` branch.pu.forcefetch Pavel Roskin
2006-12-29 2:30 ` branch.pu.forcefetch Junio C Hamano
2006-12-29 3:34 ` branch.pu.forcefetch Pavel Roskin
2006-12-29 4:31 ` branch.pu.forcefetch Shawn Pearce
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=20061229043525.GC12072@spearce.org \
--to=spearce@spearce.org \
--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 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).