From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v2 00/14] Classify {branches,remotes}-file as fringe features
Date: Sat, 22 Jun 2013 13:28:07 +0530 [thread overview]
Message-ID: <1371887901-5659-1-git-send-email-artagnon@gmail.com> (raw)
Hi,
Since I didn't explain the series properly last time: this series
reduces the burden of the branches-file/remotes-file cruft. It does
not argue for deprecation, because it is still useful to some people
and harms nobody. It removes dead code, tests the feature properly,
and doesn't mention it in obscure places.
In this iteration, [1/14] does a file-wide style cleanup (wasn't as
painful as I thought). Also, one s/git config/test_config/ patch has
been dropped because it adds no value. This time, I actually ran all
the tests to make sure that I made no silly mistakes (there were quite
a few last time).
Thanks to Junio and Eric Sunshine for reviews.
Ramkumar Ramachandra (14):
t/t5505-remote: modernize style
t/t5505-remote: test push-refspec in branches-file
t/t5505-remote: use test_path_is_missing
t/t5505-remote: remove dependency on $origin_url
remote: remove dead code in read_branches_file()
t/t5505-remote: test url-with-# in branches-file
t/t5516-fetch-push: don't use branches-file
ls-remote doc: fix example invocation on git.git
ls-remote doc: rewrite <repository> paragraph
ls-remote doc: don't encourage use of branches-file
t/t5505-remote: test multiple push/pull in remotes-file
t/t5510-fetch: don't use remotes-file
t/t5515-fetch-merge-logic: don't use {branches,remotes}-file
remote: add comment about read_{branches,remotes}_file
Documentation/git-ls-remote.txt | 11 +-
remote.c | 34 +-
t/t5505-remote.sh | 852 ++++++++++++++++++++++------------------
t/t5510-fetch.sh | 9 +-
t/t5515-fetch-merge-logic.sh | 28 +-
t/t5516-fetch-push.sh | 16 +-
6 files changed, 516 insertions(+), 434 deletions(-)
--
1.8.3.1.498.gacf2885
next reply other threads:[~2013-06-22 8:01 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-22 7:58 Ramkumar Ramachandra [this message]
2013-06-22 7:58 ` [PATCH v2 01/14] t/t5505-remote: modernize style Ramkumar Ramachandra
2013-06-23 7:42 ` Junio C Hamano
2013-06-23 7:50 ` Ramkumar Ramachandra
2013-06-22 7:58 ` [PATCH v2 02/14] t/t5505-remote: test push-refspec in branches-file Ramkumar Ramachandra
2013-06-22 7:58 ` [PATCH v2 03/14] t/t5505-remote: use test_path_is_missing Ramkumar Ramachandra
2013-06-22 7:58 ` [PATCH v2 04/14] t/t5505-remote: remove dependency on $origin_url Ramkumar Ramachandra
2013-06-22 7:58 ` [PATCH v2 05/14] remote: remove dead code in read_branches_file() Ramkumar Ramachandra
2013-06-23 7:19 ` Junio C Hamano
2013-06-22 7:58 ` [PATCH v2 06/14] t/t5505-remote: test url-with-# in branches-file Ramkumar Ramachandra
2013-06-22 7:58 ` [PATCH v2 07/14] t/t5516-fetch-push: don't use branches-file Ramkumar Ramachandra
2013-06-22 7:58 ` [PATCH v2 08/14] ls-remote doc: fix example invocation on git.git Ramkumar Ramachandra
2013-06-23 7:22 ` Junio C Hamano
2013-06-23 7:53 ` Ramkumar Ramachandra
2013-06-23 8:04 ` Junio C Hamano
2013-06-22 7:58 ` [PATCH v2 09/14] ls-remote doc: rewrite <repository> paragraph Ramkumar Ramachandra
2013-06-22 7:58 ` [PATCH v2 10/14] ls-remote doc: don't encourage use of branches-file Ramkumar Ramachandra
2013-06-22 7:58 ` [PATCH v2 11/14] t/t5505-remote: test multiple push/pull in remotes-file Ramkumar Ramachandra
2013-06-23 8:07 ` Junio C Hamano
2013-06-23 8:28 ` Ramkumar Ramachandra
2013-06-23 21:49 ` Junio C Hamano
2013-06-22 7:58 ` [PATCH v2 12/14] t/t5510-fetch: don't use remotes-file Ramkumar Ramachandra
2013-06-22 7:58 ` [PATCH v2 13/14] t/t5515-fetch-merge-logic: don't use {branches,remotes}-file Ramkumar Ramachandra
[not found] ` <CA+gHt1B1pKz5iU+9m_gi36u7g91qZqgdkY97WDAWjRGxu-Vjuw@mail.gmail.com>
2013-06-25 10:20 ` Ramkumar Ramachandra
2013-06-22 7:58 ` [PATCH v2 14/14] remote: add comment about read_{branches,remotes}_file Ramkumar Ramachandra
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1371887901-5659-1-git-send-email-artagnon@gmail.com \
--to=artagnon@gmail.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).