From: Johan Herland <johan@herland.net>
To: git@vger.kernel.org
Cc: tfnico@gmail.com, Johan Herland <johan@herland.net>
Subject: [RFC/PATCHv3 0/3] Change git-svn's default --prefix in Git v2.0
Date: Fri, 11 Oct 2013 14:57:04 +0200 [thread overview]
Message-ID: <1381496227-28700-1-git-send-email-johan@herland.net> (raw)
In-Reply-To: <1381015833-696-1-git-send-email-johan@herland.net>
Hi,
Another iteration, identical to v2, except for the fixes suggested by
Eric Sunshine.
...Johan
Johan Herland (3):
Documentation/git-svn: Promote the use of --prefix in docs + examples
git-svn: Warn about changing default for --prefix in Git v2.0
Git 2.0: git svn: Set default --prefix='origin/' if --prefix is not given
Documentation/git-svn.txt | 27 ++++++----
git-svn.perl | 2 +-
t/t9107-git-svn-migrate.sh | 54 +++++++++----------
t/t9114-git-svn-dcommit-merge.sh | 4 +-
t/t9116-git-svn-log.sh | 46 ++++++++--------
t/t9117-git-svn-init-clone.sh | 67 ++++++++++++++++++++++++
t/t9118-git-svn-funky-branch-names.sh | 20 +++----
t/t9120-git-svn-clone-with-percent-escapes.sh | 14 ++---
t/t9125-git-svn-multi-glob-branch-names.sh | 6 +--
t/t9128-git-svn-cmd-branch.sh | 18 +++----
t/t9135-git-svn-moved-branch-empty-file.sh | 2 +-
t/t9141-git-svn-multiple-branches.sh | 28 +++++-----
t/t9145-git-svn-master-branch.sh | 2 +-
t/t9155-git-svn-fetch-deleted-tag.sh | 4 +-
t/t9156-git-svn-fetch-deleted-tag-2.sh | 6 +--
t/t9161-git-svn-mergeinfo-push.sh | 22 ++++----
t/t9163-git-svn-reset-clears-caches.sh | 4 +-
t/t9165-git-svn-fetch-merge-branch-of-branch.sh | 2 +-
t/t9166-git-svn-fetch-merge-branch-of-branch2.sh | 2 +-
t/t9167-git-svn-cmd-branch-subproject.sh | 2 +-
20 files changed, 203 insertions(+), 129 deletions(-)
--
1.8.4.653.g2df02b3
next prev parent reply other threads:[~2013-10-11 12:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 9:02 git-svn: Use prefix by default? Thomas Ferris Nicolaisen
2013-09-30 22:39 ` Johan Herland
2013-09-30 22:46 ` [RFC/PATCH] git svn: Set default --prefix='origin/' if --prefix is not given Johan Herland
2013-10-01 4:07 ` Eric Wong
2013-10-01 6:12 ` Johan Herland
2013-10-03 19:01 ` Eric Wong
2013-10-05 23:30 ` [RFC/PATCHv2 1/3] Documentation/git-svn: Promote the use of --prefix in docs + examples Johan Herland
2013-10-05 23:30 ` [RFC/PATCHv2 2/3] git-svn: Warn about changing default for --prefix in Git v2.0 Johan Herland
2013-10-09 1:34 ` Eric Sunshine
2013-10-09 12:18 ` Johan Herland
2013-10-05 23:30 ` [RFC/PATCHv2 3/3] Git 2.0: git svn: Set default --prefix='origin/' if --prefix is not given Johan Herland
2013-10-06 9:51 ` [RFC/PATCHv2 1/3] Documentation/git-svn: Promote the use of --prefix in docs + examples Philip Oakley
2013-10-06 13:46 ` Johan Herland
2013-10-09 1:33 ` Eric Sunshine
2013-10-09 12:06 ` Johan Herland
2013-10-11 12:57 ` Johan Herland [this message]
2013-10-11 12:57 ` [RFC/PATCHv3 " Johan Herland
2013-10-11 12:57 ` [RFC/PATCHv3 2/3] git-svn: Warn about changing default for --prefix in Git v2.0 Johan Herland
2013-10-12 22:33 ` Eric Wong
2013-10-11 12:57 ` [RFC/PATCHv3 3/3] Git 2.0: git svn: Set default --prefix='origin/' if --prefix is not given Johan Herland
2014-04-19 8:32 ` Eric Wong
2014-04-19 9:10 ` [PATCH] git-svn.txt: Retain a description og pre-v2.0 default prefix Johan Herland
2014-04-19 11:43 ` Eric Wong
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=1381496227-28700-1-git-send-email-johan@herland.net \
--to=johan@herland.net \
--cc=git@vger.kernel.org \
--cc=tfnico@gmail.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).