Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
git
提交
80b52b0f
G
git
项目概览
李少辉-开发者
/
git
与 Fork 源项目一致
从无法访问的项目Fork
通知
2
Star
1
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
git
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
80b52b0f
编写于
9月 01, 2005
作者:
J
Junio C Hamano
浏览文件
操作
浏览文件
下载
差异文件
Merge refs/heads/master from .
上级
466fede1
2d569933
变更
4
隐藏空白更改
内联
并排
Showing
4 changed file
with
61 addition
and
31 deletion
+61
-31
Documentation/SubmittingPatches
Documentation/SubmittingPatches
+12
-0
git-commit-script
git-commit-script
+20
-25
git-log-script
git-log-script
+13
-2
git-status-script
git-status-script
+16
-4
未找到文件。
Documentation/SubmittingPatches
浏览文件 @
80b52b0f
...
...
@@ -232,6 +232,18 @@ diff --git a/pico/pico.c b/pico/pico.c
break;
(Daniel Barkalow)
> A patch to SubmittingPatches, MUA specific help section for
> users of Pine 4.63 would be very much appreciated.
Ah, it looks like a recent version changed the default behavior to do the
right thing, and inverted the sense of the configuration option. (Either
that or Gentoo did it.) So you need to set the
"no-strip-whitespace-before-send"
option, unless the option you have is
"strip-whitespace-before-send",
in which case you should avoid checking
it.
Thunderbird
-----------
...
...
git-commit-script
浏览文件 @
80b52b0f
...
...
@@ -113,21 +113,6 @@ t)
fi
esac
if
[
!
-r
"
$GIT_DIR
/HEAD"
]
then
echo
"#"
echo
"# Initial commit"
echo
"#"
git-ls-files |
sed
's/^/# New file: /'
echo
"#"
elif
[
-f
"
$GIT_DIR
/MERGE_HEAD"
]
;
then
echo
"#"
echo
"# It looks like your may be committing a MERGE."
echo
"# If this is not correct, please remove the file"
echo
"#
$GIT_DIR
/MERGE_HEAD"
echo
"# and try again"
echo
"#"
fi
>
.editmsg
if
test
"
$log_message
"
!=
''
then
echo
"
$log_message
"
...
...
@@ -144,7 +129,25 @@ then
elif
test
"
$use_commit
"
!=
""
then
git-cat-file commit
"
$use_commit
"
|
sed
-e
'1,/^$/d'
fi
| git-stripspace
>>
.editmsg
fi
| git-stripspace
>
.editmsg
case
"
$signoff
"
in
t
)
git-var GIT_COMMITTER_IDENT |
sed
-e
'
s/>.*/>/
s/^/Signed-off-by: /
'
>>
.editmsg
;;
esac
if
[
-f
"
$GIT_DIR
/MERGE_HEAD"
]
;
then
echo
"#"
echo
"# It looks like your may be committing a MERGE."
echo
"# If this is not correct, please remove the file"
echo
"#
$GIT_DIR
/MERGE_HEAD"
echo
"# and try again"
echo
"#"
fi
>>
.editmsg
PARENTS
=
"-p HEAD"
if
[
!
-r
"
$GIT_DIR
/HEAD"
]
;
then
...
...
@@ -186,16 +189,8 @@ else
export
GIT_AUTHOR_EMAIL
export
GIT_AUTHOR_DATE
fi
case
"
$signoff
"
in
t
)
git-var GIT_COMMITTER_IDENT |
sed
-e
'
s/>.*/>/
s/^/Signed-off-by: /
'
>>
.editmsg
;;
esac
git-status-script
>>
.editmsg
fi
git-status-script
>>
.editmsg
if
[
"
$?
"
!=
"0"
-a
!
-f
$GIT_DIR
/MERGE_HEAD
]
then
rm
-f
.editmsg
...
...
git-log-script
浏览文件 @
80b52b0f
#!/bin/sh
#
# Copyright (c) 2005 Linus Torvalds
#
# This one uses only subdirectory-aware commands, so no need to
# include sh-setup-script.
revs
=
$(
git-rev-parse
--revs-only
--no-flags
--default
HEAD
"
$@
"
)
||
exit
[
"
$revs
"
]
||
die
"No HEAD ref"
git-rev-list
--pretty
$(
git-rev-parse
--default
HEAD
"
$@
"
)
|
LESS
=
-S
${
PAGER
:-
less
}
[
"
$revs
"
]
||
{
echo
>
&2
"No HEAD ref"
exit
1
}
git-rev-list
--pretty
$(
git-rev-parse
--default
HEAD
"
$@
"
)
|
LESS
=
-S
${
PAGER
:-
less
}
git-status-script
浏览文件 @
80b52b0f
...
...
@@ -39,11 +39,23 @@ esac
git-update-cache
--refresh
>
/dev/null 2>&1
git-diff-cache
-M
--cached
HEAD |
sed
's/^://'
|
report
"Updated but not checked in"
"will commit"
if
test
-f
"
$GIT_DIR
/HEAD"
then
git-diff-cache
-M
--cached
HEAD |
sed
's/^://'
|
report
"Updated but not checked in"
"will commit"
committable
=
"
$?
"
committable
=
"
$?
"
else
echo
'#
# Initial commit
#'
git-ls-files |
sed
's/^/o o o o A /'
|
report
"Updated but not checked in"
"will commit"
committable
=
"
$?
"
fi
git-diff-files |
sed
's/^://'
|
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录