list mirror (unofficial, one of many)
 help / color / mirror / Atom feed
From: "Lukas Pupka-Lipinski via GitGitGadget" <>
Subject: [PATCH 0/2] GitSVN: Multi line support of ignore-path, include-paths and skiping of empty commits
Date: Fri, 11 Sep 2020 08:00:15 +0000
Message-ID: <> (raw)

[PATCH]v3 GitSVN: Multi line support of ignore-path, include-paths and
skiping of empty commits

I used the ignore-paths option to ignore a lot of stuff I don’t need. The
ignore pattern works well, but it could and up in empty commits. So just the
message without any modifications / changes. The patch below skip a commit
if all changes are ignored by the ignore-paths option. In order to use this
feature I includes the option to read configuration for ignore-path,
include-paths in several lines. So that the user is not limited by the max.
char. per line definition. In Addition this patch includes the optimizations
which are mansion from your side.

Regarding the subrouties comments i oriented by this example: 

Changes in v3:

 * Changed the code format (spaces etc.)
 * Wrap reg-expression by (?:<expression1>|<expression2>)
 * Removed useless variable init
 * Removed useless check.

Lukas (2):
  svn: added: Multi line support for ignore-paths
  sv: added: Skip commit if all files are ignored

 perl/Git/         | 21 +++++++++++++++++++++
 perl/Git/SVN/ | 42 ++++++++++++++++++++++++++++++++++++-----
 perl/Git/SVN/      |  2 ++
 3 files changed, 60 insertions(+), 5 deletions(-)

base-commit: 274b9cc25322d9ee79aa8e6d4e86f0ffe5ced925
Fetch-It-Via: git fetch pr-git-834/lukaspupkalipinski/master-v1

             reply	other threads:[~2020-09-11  8:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-11  8:00 Lukas Pupka-Lipinski via GitGitGadget [this message]
2020-09-11  8:00 ` [PATCH 1/2] svn: added: Multi line support for ignore-paths Lukas via GitGitGadget
2020-09-11  8:00 ` [PATCH 2/2] sv: added: Skip commit if all files are ignored Lukas via GitGitGadget

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror
	git clone --mirror http://ou63pmih66umazou.onion/git
	git clone --mirror http://czquwvybam4bgbro.onion/git
	git clone --mirror http://hjrcffqmbrq6wope.onion/git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 git git/ \
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
 note: .onion URLs require Tor:

code repositories for the project(s) associated with this inbox:

AGPL code for this site: git clone