new

chengbao.git

@@ -0,0 +1 @@
+Subproject commit 7095969974b74f5415ad6a19e07591fe68e41759

dumpling222.git/HEAD

@@ -0,0 +1 @@
+ref: refs/heads/master

dumpling222.git/config

@@ -0,0 +1,4 @@
+[core]
+	repositoryformatversion = 0
+	filemode = true
+	bare = true

dumpling222.git/description

@@ -0,0 +1 @@
+Unnamed repository; edit this file 'description' to name the repository.

dumpling222.git/hooks/applypatch-msg.sample

@@ -0,0 +1,15 @@
+#!/bin/sh
+#
+# An example hook script to check the commit log message taken by
+# applypatch from an e-mail message.
+#
+# The hook should exit with non-zero status after issuing an
+# appropriate message if it wants to stop the commit.  The hook is
+# allowed to edit the commit message file.
+#
+# To enable this hook, rename this file to "applypatch-msg".
+
+. git-sh-setup
+commitmsg="$(git rev-parse --git-path hooks/commit-msg)"
+test -x "$commitmsg" && exec "$commitmsg" ${1+"$@"}
+:

dumpling222.git/hooks/commit-msg.sample

@@ -0,0 +1,24 @@
+#!/bin/sh
+#
+# An example hook script to check the commit log message.
+# Called by "git commit" with one argument, the name of the file
+# that has the commit message.  The hook should exit with non-zero
+# status after issuing an appropriate message if it wants to stop the
+# commit.  The hook is allowed to edit the commit message file.
+#
+# To enable this hook, rename this file to "commit-msg".
+
+# Uncomment the below to add a Signed-off-by line to the message.
+# Doing this in a hook is a bad idea in general, but the prepare-commit-msg
+# hook is more suited to it.
+#
+# SOB=$(git var GIT_AUTHOR_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
+# grep -qs "^$SOB" "$1" || echo "$SOB" >> "$1"
+
+# This example catches duplicate Signed-off-by lines.
+
+test "" = "$(grep '^Signed-off-by: ' "$1" |
+	 sort | uniq -c | sed -e '/^[ 	]*1[ 	]/d')" || {
+	echo >&2 Duplicate Signed-off-by lines.
+	exit 1
+}

dumpling222.git/hooks/post-receive

@@ -0,0 +1,2 @@
+#!/usr/bin/env bash
+"/app/gogs/gogs" hook --config='/data/gogs/conf/app.ini' post-receive

dumpling222.git/hooks/post-update.sample

@@ -0,0 +1,8 @@
+#!/bin/sh
+#
+# An example hook script to prepare a packed repository for use over
+# dumb transports.
+#
+# To enable this hook, rename this file to "post-update".
+
+exec git update-server-info

dumpling222.git/hooks/pre-applypatch.sample

@@ -0,0 +1,14 @@
+#!/bin/sh
+#
+# An example hook script to verify what is about to be committed
+# by applypatch from an e-mail message.
+#
+# The hook should exit with non-zero status after issuing an
+# appropriate message if it wants to stop the commit.
+#
+# To enable this hook, rename this file to "pre-applypatch".
+
+. git-sh-setup
+precommit="$(git rev-parse --git-path hooks/pre-commit)"
+test -x "$precommit" && exec "$precommit" ${1+"$@"}
+:

dumpling222.git/hooks/pre-commit.sample

@@ -0,0 +1,49 @@
+#!/bin/sh
+#
+# An example hook script to verify what is about to be committed.
+# Called by "git commit" with no arguments.  The hook should
+# exit with non-zero status after issuing an appropriate message if
+# it wants to stop the commit.
+#
+# To enable this hook, rename this file to "pre-commit".
+
+if git rev-parse --verify HEAD >/dev/null 2>&1
+then
+	against=HEAD
+else
+	# Initial commit: diff against an empty tree object
+	against=$(git hash-object -t tree /dev/null)
+fi
+
+# If you want to allow non-ASCII filenames set this variable to true.
+allownonascii=$(git config --bool hooks.allownonascii)
+
+# Redirect output to stderr.
+exec 1>&2
+
+# Cross platform projects tend to avoid non-ASCII filenames; prevent
+# them from being added to the repository. We exploit the fact that the
+# printable range starts at the space character and ends with tilde.
+if [ "$allownonascii" != "true" ] &&
+	# Note that the use of brackets around a tr range is ok here, (it's
+	# even required, for portability to Solaris 10's /usr/bin/tr), since
+	# the square bracket bytes happen to fall in the designated range.
+	test $(git diff --cached --name-only --diff-filter=A -z $against |
+	  LC_ALL=C tr -d '[ -~]\0' | wc -c) != 0
+then
+	cat <<\EOF
+Error: Attempt to add a non-ASCII file name.
+
+This can cause problems if you want to work with people on other platforms.
+
+To be portable it is advisable to rename the file.
+
+If you know what you are doing you can disable this check using:
+
+  git config hooks.allownonascii true
+EOF
+	exit 1
+fi
+
+# If there are whitespace errors, print the offending file names and fail.
+exec git diff-index --check --cached $against --

dumpling222.git/hooks/pre-merge-commit.sample

@@ -0,0 +1,13 @@
+#!/bin/sh
+#
+# An example hook script to verify what is about to be committed.
+# Called by "git merge" with no arguments.  The hook should
+# exit with non-zero status after issuing an appropriate message to
+# stderr if it wants to stop the merge commit.
+#
+# To enable this hook, rename this file to "pre-merge-commit".
+
+. git-sh-setup
+test -x "$GIT_DIR/hooks/pre-commit" &&
+        exec "$GIT_DIR/hooks/pre-commit"
+:

dumpling222.git/hooks/pre-push.sample

@@ -0,0 +1,53 @@
+#!/bin/sh
+
+# An example hook script to verify what is about to be pushed.  Called by "git
+# push" after it has checked the remote status, but before anything has been
+# pushed.  If this script exits with a non-zero status nothing will be pushed.
+#
+# This hook is called with the following parameters:
+#
+# $1 -- Name of the remote to which the push is being done
+# $2 -- URL to which the push is being done
+#
+# If pushing without using a named remote those arguments will be equal.
+#
+# Information about the commits which are being pushed is supplied as lines to
+# the standard input in the form:
+#
+#   <local ref> <local sha1> <remote ref> <remote sha1>
+#
+# This sample shows how to prevent push of commits where the log message starts
+# with "WIP" (work in progress).
+
+remote="$1"
+url="$2"
+
+z40=0000000000000000000000000000000000000000
+
+while read local_ref local_sha remote_ref remote_sha
+do
+	if [ "$local_sha" = $z40 ]
+	then
+		# Handle delete
+		:
+	else
+		if [ "$remote_sha" = $z40 ]
+		then
+			# New branch, examine all commits
+			range="$local_sha"
+		else
+			# Update to existing branch, examine new commits
+			range="$remote_sha..$local_sha"
+		fi
+
+		# Check for WIP commit
+		commit=`git rev-list -n 1 --grep '^WIP' "$range"`
+		if [ -n "$commit" ]
+		then
+			echo >&2 "Found WIP commit in $local_ref, not pushing"
+			exit 1
+		fi
+	fi
+done
+
+exit 0

dumpling222.git/hooks/pre-rebase.sample

@@ -0,0 +1,169 @@
+#!/bin/sh
+#
+# Copyright (c) 2006, 2008 Junio C Hamano
+#
+# The "pre-rebase" hook is run just before "git rebase" starts doing
+# its job, and can prevent the command from running by exiting with
+# non-zero status.
+#
+# The hook is called with the following parameters:
+#
+# $1 -- the upstream the series was forked from.
+# $2 -- the branch being rebased (or empty when rebasing the current branch).
+#
+# This sample shows how to prevent topic branches that are already
+# merged to 'next' branch from getting rebased, because allowing it
+# would result in rebasing already published history.
+
+publish=next
+basebranch="$1"
+if test "$#" = 2
+then
+	topic="refs/heads/$2"
+else
+	topic=`git symbolic-ref HEAD` ||
+	exit 0 ;# we do not interrupt rebasing detached HEAD
+fi
+
+case "$topic" in
+refs/heads/??/*)
+	;;
+*)
+	exit 0 ;# we do not interrupt others.
+	;;
+esac
+
+# Now we are dealing with a topic branch being rebased
+# on top of master.  Is it OK to rebase it?
+
+# Does the topic really exist?
+git show-ref -q "$topic" || {
+	echo >&2 "No such branch $topic"
+	exit 1
+}
+
+# Is topic fully merged to master?
+not_in_master=`git rev-list --pretty=oneline ^master "$topic"`
+if test -z "$not_in_master"
+then
+	echo >&2 "$topic is fully merged to master; better remove it."
+	exit 1 ;# we could allow it, but there is no point.
+fi
+
+# Is topic ever merged to next?  If so you should not be rebasing it.
+only_next_1=`git rev-list ^master "^$topic" ${publish} | sort`
+only_next_2=`git rev-list ^master           ${publish} | sort`
+if test "$only_next_1" = "$only_next_2"
+then
+	not_in_topic=`git rev-list "^$topic" master`
+	if test -z "$not_in_topic"
+	then
+		echo >&2 "$topic is already up to date with master"
+		exit 1 ;# we could allow it, but there is no point.
+	else
+		exit 0
+	fi
+else
+	not_in_next=`git rev-list --pretty=oneline ^${publish} "$topic"`
+	/usr/bin/perl -e '
+		my $topic = $ARGV[0];
+		my $msg = "* $topic has commits already merged to public branch:\n";
+		my (%not_in_next) = map {
+			/^([0-9a-f]+) /;
+			($1 => 1);
+		} split(/\n/, $ARGV[1]);
+		for my $elem (map {
+				/^([0-9a-f]+) (.*)$/;
+				[$1 => $2];
+			} split(/\n/, $ARGV[2])) {
+			if (!exists $not_in_next{$elem->[0]}) {
+				if ($msg) {
+					print STDERR $msg;
+					undef $msg;
+				}
+				print STDERR " $elem->[1]\n";
+			}
+		}
+	' "$topic" "$not_in_next" "$not_in_master"
+	exit 1
+fi
+
+<<\DOC_END
+
+This sample hook safeguards topic branches that have been
+published from being rewound.
+
+The workflow assumed here is:
+
+ * Once a topic branch forks from "master", "master" is never
+   merged into it again (either directly or indirectly).
+
+ * Once a topic branch is fully cooked and merged into "master",
+   it is deleted.  If you need to build on top of it to correct
+   earlier mistakes, a new topic branch is created by forking at
+   the tip of the "master".  This is not strictly necessary, but
+   it makes it easier to keep your history simple.
+
+ * Whenever you need to test or publish your changes to topic
+   branches, merge them into "next" branch.
+
+The script, being an example, hardcodes the publish branch name
+to be "next", but it is trivial to make it configurable via
+$GIT_DIR/config mechanism.
+
+With this workflow, you would want to know:
+
+(1) ... if a topic branch has ever been merged to "next".  Young
+    topic branches can have stupid mistakes you would rather
+    clean up before publishing, and things that have not been
+    merged into other branches can be easily rebased without
+    affecting other people.  But once it is published, you would
+    not want to rewind it.
+
+(2) ... if a topic branch has been fully merged to "master".
+    Then you can delete it.  More importantly, you should not
+    build on top of it -- other people may already want to
+    change things related to the topic as patches against your
+    "master", so if you need further changes, it is better to
+    fork the topic (perhaps with the same name) afresh from the
+    tip of "master".
+
+Let's look at this example:
+
+		   o---o---o---o---o---o---o---o---o---o "next"
+		  /       /           /           /
+		 /   a---a---b A     /           /
+		/   /               /           /
+	       /   /   c---c---c---c B         /
+	      /   /   /             \         /
+	     /   /   /   b---b C     \       /
+	    /   /   /   /             \     /
+    ---o---o---o---o---o---o---o---o---o---o---o "master"
+
+
+A, B and C are topic branches.
+
+ * A has one fix since it was merged up to "next".
+
+ * B has finished.  It has been fully merged up to "master" and "next",
+   and is ready to be deleted.
+
+ * C has not merged to "next" at all.
+
+We would want to allow C to be rebased, refuse A, and encourage
+B to be deleted.
+
+To compute (1):
+
+	git rev-list ^master ^topic next
+	git rev-list ^master        next
+
+	if these match, topic has not merged in next at all.
+
+To compute (2):
+
+	git rev-list master..topic
+
+	if this is empty, it is fully merged to "master".
+
+DOC_END

dumpling222.git/hooks/pre-receive

@@ -0,0 +1,2 @@
+#!/usr/bin/env bash
+"/app/gogs/gogs" hook --config='/data/gogs/conf/app.ini' pre-receive

dumpling222.git/hooks/pre-receive.sample

@@ -0,0 +1,24 @@
+#!/bin/sh
+#
+# An example hook script to make use of push options.
+# The example simply echoes all push options that start with 'echoback='
+# and rejects all pushes when the "reject" push option is used.
+#
+# To enable this hook, rename this file to "pre-receive".
+
+if test -n "$GIT_PUSH_OPTION_COUNT"
+then
+	i=0
+	while test "$i" -lt "$GIT_PUSH_OPTION_COUNT"
+	do
+		eval "value=\$GIT_PUSH_OPTION_$i"
+		case "$value" in
+		echoback=*)
+			echo "echo from the pre-receive-hook: ${value#*=}" >&2
+			;;
+		reject)
+			exit 1
+		esac
+		i=$((i + 1))
+	done
+fi

dumpling222.git/hooks/prepare-commit-msg.sample

@@ -0,0 +1,42 @@
+#!/bin/sh
+#
+# An example hook script to prepare the commit log message.
+# Called by "git commit" with the name of the file that has the
+# commit message, followed by the description of the commit
+# message's source.  The hook's purpose is to edit the commit
+# message file.  If the hook fails with a non-zero status,
+# the commit is aborted.
+#
+# To enable this hook, rename this file to "prepare-commit-msg".
+
+# This hook includes three examples. The first one removes the
+# "# Please enter the commit message..." help message.
+#
+# The second includes the output of "git diff --name-status -r"
+# into the message, just before the "git status" output.  It is
+# commented because it doesn't cope with --amend or with squashed
+# commits.
+#
+# The third example adds a Signed-off-by line to the message, that can
+# still be edited.  This is rarely a good idea.
+
+COMMIT_MSG_FILE=$1
+COMMIT_SOURCE=$2
+SHA1=$3
+
+/usr/bin/perl -i.bak -ne 'print unless(m/^. Please enter the commit message/..m/^#$/)' "$COMMIT_MSG_FILE"
+
+# case "$COMMIT_SOURCE,$SHA1" in
+#  ,|template,)
+#    /usr/bin/perl -i.bak -pe '
+#       print "\n" . `git diff --cached --name-status -r`
+# 	 if /^#/ && $first++ == 0' "$COMMIT_MSG_FILE" ;;
+#  *) ;;
+# esac
+
+# SOB=$(git var GIT_COMMITTER_IDENT | sed -n 's/^\(.*>\).*$/Signed-off-by: \1/p')
+# git interpret-trailers --in-place --trailer "$SOB" "$COMMIT_MSG_FILE"
+# if test -z "$COMMIT_SOURCE"
+# then
+#   /usr/bin/perl -i.bak -pe 'print "\n" if !$first_line++' "$COMMIT_MSG_FILE"
+# fi

dumpling222.git/hooks/update

@@ -0,0 +1,2 @@
+#!/usr/bin/env bash
+"/app/gogs/gogs" hook --config='/data/gogs/conf/app.ini' update $1 $2 $3

dumpling222.git/hooks/update.sample

@@ -0,0 +1,128 @@
+#!/bin/sh
+#
+# An example hook script to block unannotated tags from entering.
+# Called by "git receive-pack" with arguments: refname sha1-old sha1-new
+#
+# To enable this hook, rename this file to "update".
+#
+# Config
+# ------
+# hooks.allowunannotated
+#   This boolean sets whether unannotated tags will be allowed into the
+#   repository.  By default they won't be.
+# hooks.allowdeletetag
+#   This boolean sets whether deleting tags will be allowed in the
+#   repository.  By default they won't be.
+# hooks.allowmodifytag
+#   This boolean sets whether a tag may be modified after creation. By default
+#   it won't be.
+# hooks.allowdeletebranch
+#   This boolean sets whether deleting branches will be allowed in the
+#   repository.  By default they won't be.
+# hooks.denycreatebranch
+#   This boolean sets whether remotely creating branches will be denied
+#   in the repository.  By default this is allowed.
+#
+
+# --- Command line
+refname="$1"
+oldrev="$2"
+newrev="$3"
+
+# --- Safety check
+if [ -z "$GIT_DIR" ]; then
+	echo "Don't run this script from the command line." >&2
+	echo " (if you want, you could supply GIT_DIR then run" >&2
+	echo "  $0 <ref> <oldrev> <newrev>)" >&2
+	exit 1
+fi
+
+if [ -z "$refname" -o -z "$oldrev" -o -z "$newrev" ]; then
+	echo "usage: $0 <ref> <oldrev> <newrev>" >&2
+	exit 1
+fi
+
+# --- Config
+allowunannotated=$(git config --bool hooks.allowunannotated)
+allowdeletebranch=$(git config --bool hooks.allowdeletebranch)
+denycreatebranch=$(git config --bool hooks.denycreatebranch)
+allowdeletetag=$(git config --bool hooks.allowdeletetag)
+allowmodifytag=$(git config --bool hooks.allowmodifytag)
+
+# check for no description
+projectdesc=$(sed -e '1q' "$GIT_DIR/description")
+case "$projectdesc" in
+"Unnamed repository"* | "")
+	echo "*** Project description file hasn't been set" >&2
+	exit 1
+	;;
+esac
+
+# --- Check types
+# if $newrev is 0000...0000, it's a commit to delete a ref.
+zero="0000000000000000000000000000000000000000"
+if [ "$newrev" = "$zero" ]; then
+	newrev_type=delete
+else
+	newrev_type=$(git cat-file -t $newrev)
+fi
+
+case "$refname","$newrev_type" in
+	refs/tags/*,commit)
+		# un-annotated tag
+		short_refname=${refname##refs/tags/}
+		if [ "$allowunannotated" != "true" ]; then
+			echo "*** The un-annotated tag, $short_refname, is not allowed in this repository" >&2
+			echo "*** Use 'git tag [ -a | -s ]' for tags you want to propagate." >&2
+			exit 1
+		fi
+		;;
+	refs/tags/*,delete)
+		# delete tag
+		if [ "$allowdeletetag" != "true" ]; then
+			echo "*** Deleting a tag is not allowed in this repository" >&2
+			exit 1
+		fi
+		;;
+	refs/tags/*,tag)
+		# annotated tag
+		if [ "$allowmodifytag" != "true" ] && git rev-parse $refname > /dev/null 2>&1
+		then
+			echo "*** Tag '$refname' already exists." >&2
+			echo "*** Modifying a tag is not allowed in this repository." >&2
+			exit 1
+		fi
+		;;
+	refs/heads/*,commit)
+		# branch
+		if [ "$oldrev" = "$zero" -a "$denycreatebranch" = "true" ]; then
+			echo "*** Creating a branch is not allowed in this repository" >&2
+			exit 1
+		fi
+		;;
+	refs/heads/*,delete)
+		# delete branch
+		if [ "$allowdeletebranch" != "true" ]; then
+			echo "*** Deleting a branch is not allowed in this repository" >&2
+			exit 1
+		fi
+		;;
+	refs/remotes/*,commit)
+		# tracking branch
+		;;
+	refs/remotes/*,delete)
+		# delete tracking branch
+		if [ "$allowdeletebranch" != "true" ]; then
+			echo "*** Deleting a tracking branch is not allowed in this repository" >&2
+			exit 1
+		fi
+		;;
+	*)
+		# Anything else (is there anything else?)
+		echo "*** Update hook: unknown type of update to ref $refname of type $newrev_type" >&2
+		exit 1
+		;;
+esac
+
+# --- Finished
+exit 0

dumpling222.git/info/exclude

@@ -0,0 +1,6 @@
+# git ls-files --others --exclude-from=.git/info/exclude
+# Lines that start with '#' are comments.
+# For a project mostly in C, the following would be a good set of
+# exclude patterns (uncomment them if you want to use them):
+# *.[oa]
+# *~

dumpling222.git/info/refs

@@ -0,0 +1,2 @@
+0f180ec2f5da539a57d570aeeb33c063bddac564	refs/heads/master
+6330c7437a7f993964f5af4cb853f148515667ea	refs/heads/online-aoteman

dumpling222.git/objects/19/59053405c6abbaaa2f5d6dc41a21faa9db0a99

@@ -0,0 +1,5 @@
+x
}SЭNѓ0хQLЇСфFy‚]љhўЖR\-53в¦Щ»ыµґР:Э
cрОщО9mЦЫж’`В/ѕС§Yх-ЄrB3t;4wjЯ;…Є§йПР
UЬґКи¶GХ"CќЬАZК®¦(C{ш.ЋЩ„b#Љ’яPм/T‰ЊрИќ®ыБ`e"&,e%и
РhцBu­UіЕ|d%±RaГH)А?
›нкp
+#"я
#¶°Avєnбъ"Ќv‚lМ#ц$Z{уr–ќЗІїS“€Юspдu	< к
+t»ыЗсЮКaчш~�Gс1°(И¬>A7јф
30"е…“
+”lhОP‚!	%Ф$$Бв-Ґ5#Ўд@ђPєЖ№‘3”з¶9Й–ЦЕ„’ЃА™ТgЈ‡…У
+Т8[AЯ#–dIC“Ш6/fиКИоmрa¦РВ·ЧЪђ"ЋЙµЧџ4[ьзyОќЭ°©ъ0k	‹љЌФкFЪіЌґ{XчjэЮitь
хП)Ъ

dumpling222.git/objects/21/ed0fc5f2c47e53154dcbebd0f4a10d8d3e8aa6

@@ -0,0 +1,3 @@
+x
m‘MNĂ0…YűŁ€�
é$•±DŽ;1g¦š8@Tĺ,Yp.çŔIŁş)xYď{/óăÂs
ÇG'®Z±¸Đ޶uŔ
+Já
+f‡Ůą™¬‡Ăgă�ÍŐ�:ĺvkLQH´Wš´E™şvŔŽ[¸Yť1aď˙$¦0Ąn°ćFĚ˙uö`L)|ëÇ]wJ-Ńx-6nB{X+�ÇQ@)µA¸w´ä×Qî‘­ňaKăDóÁß©sŘ«” 5cÓî-¸Í!î,)OuŮ�	Ž)‡óń–hńŕę+,CłGM	eŮĎű×÷çǶ-»}ŃMß›·p·7ëBóxíu‹rI%ďMÎ<SüQuG6ŐłHKŚłQS(I×/:hą?ŤtŞSżC„Ćg

dumpling222.git/objects/32/a67f8acd1cf227b68319ed28a638845b77771c

@�
�
�

dumpling222.git/objects/33/32219d1b824297503c1fa5cc9d787ec3d2d289

@@ -0,0 +1,3 @@
+x
•‘ASƒ0…=χWt8K(…βMOμEλ¨Η
lJΖΠdΒbνtϊί%I+ΕιΕΓ|ϋvχν“�Mσ<½9L¦ΣΰMp7
’Ω|6n-ι:QYΗΌ(9Ω2fa�@d&YQ•Θ‘g9ψΪk΄­6‚Π³�
½R•γ¥„F{Μ…$4ηRl�―iƒM'IhΉΏ—Ί†~$ΩΆsµΑνJθt;ΒΚO`�®!Σy©–@\™ζ‰ΔvcG7¤νΨ
+	ιOν�MmΡύYΔ³h–:KNrΞ£b#π"�ςΒt�Fα2�"¬
+–/³2f‹Ψ'θΊμΦψM�ΑΧ�ζιϊΙ�f}ΚµμZRΝΰΘΥjƒm­¤}�Ψη·*BΛ~“s\qή"½χ<ϊΥzφ1bvςXeΙX³Υvk4Μ�Qljϊϋή®h{όxMΞ”©Π¬•9ςτA‘Mΰ�Ύ/<!·k'?�μόςι�..ϋ=N�?!OΜΙ

dumpling222.git/objects/38/9cada3dfed19abecba363fc78588af965ebce0

@@ -0,0 +1,2 @@
+x
�•ÑŽÓ0Eù4Ï
elÇ©óû¸H€Š\6$A»)*‰è‚öß™qì¬ãlÕÂK•¶ß9w®�ýýaÿw¨_ý�_ýÝØAU ÈàÝ´ßœÆéØ@õyùKeð•6tMßv#Teƒ} Epc‡Z@'¨„Ο²¥Hº¢rw®H¾T„¦peBEuhh//×NvhëŽ>¿Ú~þâ7BÖ¦61ƒoGêí#ToÂó§ùÙ“*êÞ-ù0“«LS‰—²uÛì9ùÕ7ž]S7D+wŽ–…Ò51'wcQÌÉÕ`§&êµ*C­U©iRE³»šS†¶<§Œ<eÅqê·˜ì
+	*a¼ ÏßµtÞY�¯!5A/ŒÏC´5+nÉRe@ÔdÑEfŠmUÔAPd‚#¦¦4mR”æ‹$=E”ž‚ºY)ªT‘bEÂ"zÞT|÷cÄœj£!‡ÅŸ]3Œ}*iÈE’Ä"@^–Ä"‰2YÐ*Žëx˜REÁébÉUÎS.³ö”š:‚2†ü=õõf�rfŒl½"­ˆI\‘¯ÀE4žå£¿åVG’³F”BKÏÉ—×…¼"&ñAŒòSÆ ¬¹9#å“3‚":$ìó –Üx«©ÜaÆ·»àÒݧë`w¿×]o‡ïïçàš¡l/Ê(	eœ<w=oÚ5óT8î_ž[so·ÀÙG;Pkýƒm›[Ëo?°îÇzlNo-<ýqÚš

dumpling222.git/objects/38/a4d7ea75d8622b1516277afc9a513d545e9113

@@ -0,0 +1,3 @@
+x
•‘ASÂ0…=ó+ΖiiiÀ›ž<ÈEqÔã¦ÝÐŒ)ɤ[‘aøï6	Xêpñ’É|ûv÷å…+ÍÇŒe7‡Ñx<ùB;¹OfÓtšNni[YzÄ8fyG™`¬;�³(OY™#$‡Eè ½A×Ñ+	ÛY0+]z^(¨MÀB*B{.p©äÁ†š±X·Š¤Qû{e*èF
+P
zWÜ®¤©Á4l ø®Ü²m�$´­_�Hn7®ápôCš–¯�À“î©ÝcSWô×>‹dO3oÉKÎy,Óx>‡e‰¢QÏâX
Ñ,I6Ã8Éè»,ìÖøM­Å×ÿæé·’•õú”kÑ6¤ë~¶¯U›J+÷U‰{œï²š€Ð±ßä<×B4Hï�µ�}˜›<T92ÔìdI•Û÷³*”›ŠþÀ.‚·+Ú?^“smK´kmŽ}Ð临
+O(ÜÚÞIÀÏ';=¿üú£�Ë�ÇÑñf´Ë

dumpling222.git/objects/4c/ec672ab50f7c2b7808d4a6b14e2ae95c93008f

@@ -0,0 +1 @@
+x
+)JMU07g040031Qðröu÷×+)f8*ºT‘oG‘õîí"qÏûu-�äÑËM-Idð}«÷d͇;Ø~_¼àUeÁ.™I‹
¢K F

dumpling222.git/objects/4d/ed2ee4acf0a8b807a1f7a3a0ea7970ba1c92a3

@@ -0,0 +1,2 @@
+x
uŽ± E�û„Y°P¡»ƒƒÆÍ«!!%)Ð¥é¿vp0®çäž\ãƒAL�kƒ^`Ƭ¥­ÀÇJrv¶"ŨÑ=¢dÇ	çÂ){K@œ(Œ�UT«}áâÃç—›ÊjÔ>Â'ヶ;¾NO0Å¥9ÿª»Nn�öb]
+õà·³¹AÒ±Àuk¶7cî;¼

dumpling222.git/objects/5e/b2188f74a438c844bf63510864d5f23e943a17

@@ -0,0 +1,3 @@
+x
•’KSÂ0…]ó+Ö–ˇhq§+˛QuĺÜ´74š’Lz+0˙Ý&
J6nşřî9÷qR&¦Ytł‡Ł4Ł»á(ÇăxtkIÓ�¢0›Ąldń4
+Îó`ž§ń4źCBrď ťF먵„žmč…*Ď%TÚc.$ˇ9��bŤ`|M¬IBËÝ˝Ô%´-9ČÝV+\/„®@×=¬!˙&í2Ť—j	Ä•©^�H¬WÖ°?¸&uĂHŕH{j{l!ľ|n­Čˇ.“p<'n5'=ĺ’gń¤�c𔷹̰"J‚I¦€i
+	gťËŔf‰[jľţ7W7•Ś¨–Ç|ó¦&Uu˝]­4X—JÚ'í‘Îe
ˇeçWś×Hď-źśµž}ô�íÜWYŇ×lDAe뚆ѹW‰bUŇŘFđvEŰâÇkr¦L�f©to#OŮ.×÷…'ävlw•ÇĎÇu:~ů\\ö{~
±łĎ�

dumpling222.git/objects/61/c25250d699e47a4bc262b7ad356977370a63dc

@@ -0,0 +1 @@
+x
=ÌA „a×=yki„b_ôºñóLcM�ˆ›¦wlâö›ü#ã$Êt¼™¥è^tTdÚ]kh[%çÁW�wì4;í¬ë5DŒ¶6²…ôˆ~¿CºdyâzÇ-”2bLáw•þ|Æ£N´ÅOá�Td^šåˈ'Î

dumpling222.git/objects/77/2b13fd1c7e9ff56aa46f7b5a8e53938d953b37

@@ -0,0 +1,2 @@
+x
­ŽK
+1D]çÙC>�tD¼J;ÎÈüˆÁÛ›�pUð ^UÞ–ejÒ ?µÊ,³Õ–I{ ¬î&)TŠÕJ%HÅaBË.š`Å+¯MH>0xî჋…³IŽ"–‚m¯h4@ âÑÆ­ÊùýœÖ<òú� >dÐ�P‡@·ãÅõ5¬[å}þ�©�Gò¶\¥öHšX%ÏŠ”�öû�ÿ.é˜æ»øz6W;

dumpling222.git/objects/7d/0abad19368447a5e5bd23e53118148d7c062af

@@ -0,0 +1 @@
+x
­Î±mĂ0@ŃÔś‚˝
Aä‘Ç#`Yĺ(-–dP”
ďá.@ę¬��’¬wY í+>ţ°ÎóÔ´%|jUD[qś92#A¤Ľw#ô¶¤Ą€+&ŞWYšÁ&%›!H,Ĺ#łĂ’g(G	‚⽍kŐçëë´Ł,'}tDmđ‡?41ŇËľIÝşe­r9ßşÓÔĆ=uĂ:?k��¬s�Fzę{őĐÇ~“«ďűç×ŰűĎý#ń&čÔ/ܵ^i

dumpling222.git/objects/ac/cef0fc0d674be7124506df7ab21bc10e7ea1bd

@@ -0,0 +1,4 @@
+x
•‘ASƒ0…=÷W0œ¥�–âMOìEë¨Ç6%ch2a±v:üwIÒJqzñÂ0ß¾Ý}û¤bAžg7ÇY„_`» $ótž†·–t�¨,Z²œÇ+�²ˆ²¢ Q
ù""˪È
+’ÄK ¾lG«�@ðlo¨^«ÊñRÒF{Ì…D0çRì€_ÓšN¢Ðòp/uM‡‘œÊœ«-ìÖB7T·¬iùI™´kÐt^ª%E®Lóˆb·µ
ÇÞ
i;¶¤Ž§Ç&¶è~Ç,’y<Ïœ%'9çQ¥Ù‚.Ê4â+B£Œ%ÑŒ¥¤c@ƒ2»Ýoà;¯ÿÍÓmE#šÍ)ײkQ5ãlW«
´µ’ö©{œë2
+)‚e¿É9®8o
ßÿj=û˜0;yª²dªÙ‹
+k»5gÕ ¶5þ�CoW´~¼&gÊT`6JOyú Ð&pißž€Ûµ£�ŸOvF~ùô½‹Ë~ûYÿÖË	

dumpling222.git/objects/d1/d8861665de41f7634e7aae0a8ae4acb7032784

@@ -0,0 +1 @@
+x
•’1OÃ0…™û+ªÎ¤ŠÛ4MØ`b 
:ÇçÆ©-çBA¨ÿ�؆† –ß½wy÷®
Ÿ®‹åÙÇd:�½¢›]Lg‹ùr¾œ�{ÒuJxTI¶*¦IÊ&_C®ÆE‘
�D½[ôŽÖ:EÙÁ�Ýx¥¡±K¥	Ý÷€+­ö.άæӤ¬~¿Ô¶†~¥ÝbHµÃýFÙl;ªàÚ¿†\¥VIãš;$Rû�7|Ã’¶ã$¤?µ?–@éÎ<¾yU`C)lžÎ³�-h¿‹YA¾dëU‘¤%–IVò2
dyy™"2+«Áåà°Å7êÞÿ·Ø˜Ð©fûUpÕµdša7ùYí°­�öߌù+ƒËBÏNn¤l‘{žž´‘=�˜ß<Vy2Ö” ºw­Øâ´«Fµ«éì+xøCÛãë¿äÜ8�nkì(Q¤W†|?ãÇÁ
JÿÚ᪈o¿âüç?puùçqrüóÑL

dumpling222.git/objects/d4/cc6108403a665f8deef4d8a0ec7430e18e5255

@@ -0,0 +1 @@
+x
+)JMU04·`040031QpOĚM
®,.IÍŐ+)fŘłq]ë.W;WîëVîĆ›¤#=ś+�±)ÔËM-Idř6KCÚřwTř,ćŰ“öň”»ä&żĽUśźśťZ�“X™Z2Řß+ˇ×íŕÁy&j'ĎT™övs8vĄŁůLÚýżľ‰ÚňG:÷őyŰ
˝<~źL
laG

dumpling222.git/objects/f1/f14666f1141726ed7e6ec793b55f268813c055

@@ -0,0 +1 @@
+x
=ÌA‚0…aל¢™5%-4êxÝx‚™a4DŒÆZ7„»ÛBÂö{ù�/6¾;ì¦ÊøéN|ãu‘”†¾PËÊ*ǽeF´Á±Ø9²-i�€("ºC¼&~“<讹¼Ñu¹Š_èY&XƒìgýRÌ2ÍÕüóy(9