From: Paolo Bonzini <bonzini@gnu.org>
To: <git@vger.kernel.org>
Subject: [PATCH 0/6] Tracking setup improvements: per-remote config, autosetuppush
Date: Sun, 12 Jul 2009 14:17:27 +0200 [thread overview]
Message-ID: <1247401053-20429-1-git-send-email-bonzini@gnu.org> (raw)
This patch series adds two features that are a step toward providing
consistent per-remote configuration of push behavior in addition
to merge (tracking) behavior.
In particular, the two features are:
1) per-remote configuration of automatic tracking setup. This leads
to some nice refactoring of the code handling autosetup, where the
combination of autosetupmerge and autosetuprebase is consolidated in
a struct.
2) The ability to automatically setup push refspecs corresponding
to local branches tracking a remote. This is false by default, since
we also have push.default---and actually, a generalized default of
true is probably not a good idea, unlike a per-remote setting. In
the future, 'git remote add' might set the per-remote autosetuppush
to true if it gets some appropriate command-line argument.
Patch 1 is a somewhat tangential DWIM that I've meant to send for
a while. It conflicts with this patch series, so I've included it.
Patches 2 and 3 include the refactorings in preparation for the new
remote.*.autosetup configuration, which is then implemented by
patch 4.
Patch 5 extracts some code to a function that will become more
complicated in patch 6. Patch 6 implements autosetuppush by
automatically creating and deleting push refspecs upon branch
creation and deletion.
config: allow false and true values for branch.autosetuprebase
branch: install_branch_config and struct tracking refactoring
introduce a struct tracking_config
remote: add per-remote autosetupmerge and autosetuprebase configuration
move deletion of merge configuration to branch.c
branch, checkout: introduce autosetuppush
Documentation/config.txt | 36 +++++++++++++++++-
branch.c | 92 +++++++++++++++++++++++++++++++++++++--------
branch.h | 5 ++-
builtin-branch.c | 10 +----
builtin-checkout.c | 2 +-
builtin-clone.c | 4 +-
cache.h | 11 ++++-
config.c | 48 +++++++++++++++++-------
environment.c | 7 ++-
remote.c | 3 +
remote.h | 1 +
t/t3200-branch.sh | 92 ++++++++++++++++++++++++++++++++++++++++++++-
12 files changed, 259 insertions(+), 52 deletions(-)
next reply other threads:[~2009-07-12 12:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-12 12:17 Paolo Bonzini [this message]
2009-07-12 12:17 ` [PATCH 1/6] config: allow false and true values for branch.autosetuprebase Paolo Bonzini
2009-07-12 12:17 ` [PATCH 2/6] branch: install_branch_config and struct tracking refactoring Paolo Bonzini
2009-07-12 12:17 ` [PATCH 3/6] introduce a struct tracking_config Paolo Bonzini
2009-07-12 12:17 ` [PATCH 4/6] remote: add per-remote autosetupmerge and autosetuprebase configuration Paolo Bonzini
2009-07-12 12:17 ` [PATCH 5/6] move deletion of merge configuration to branch.c Paolo Bonzini
2009-07-12 12:17 ` [PATCH 6/6] branch, checkout: introduce autosetuppush Paolo Bonzini
2009-07-12 21:17 ` [PATCH 0/6] Tracking setup improvements: per-remote config, autosetuppush Junio C Hamano
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=1247401053-20429-1-git-send-email-bonzini@gnu.org \
--to=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 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).