blocks|key|828519|text|引用Git常见问题的话|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|828520|git有关键字扩展吗？
不推荐使用。关键字扩展会导致各种奇怪的问题，而且实际上并不有用，特别是在SCM的上下文中。在git之外，您可以使用脚本执行关键字扩展。Linux内核导出脚本这样做是为了在Makefile中设置EXTRA_VERSION变量。
如果您真的想这样做，请参见gitattributes(5)。如果您的翻译是不可逆的(例如SCCS关键字扩展)，这可能会有问题。|blockquote|828521|entityMap|0|LINK|mutability|MUTABLE|url|https://git.wiki.kernel.org/index.php/GitFaq#Does_git_have_keyword_expansion.3F^0|2|7|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@$A|P|B|Q|1|R]]|C|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|C|$]]|$1|G|3|-4|5|6|7|T|8|@]|9|@]|C|$]]]|H|$I|$5|J|K|L|C|$M|N]]]]

Quoting from the <a href="https://git.wiki.kernel.org/index.php/GitFaq#Does_git_have_keyword_expansion.3F" rel="noreferrer">Git FAQ</a>:
<blockquote>
Does git have keyword expansion?
Not recommended. Keyword expansion causes all sorts of strange problems and
isn't really useful anyway, especially within the context of an SCM. Outside
git you may perform keyword expansion using a script. The Linux kernel export
script does this to set the EXTRA_VERSION variable in the Makefile.
See gitattributes(5) if you really want to do this. If your translation is not
reversible (eg SCCS keyword expansion) this may be problematic.
</blockquote>

blocks|key|123272|text|我在其他地方为此编写了一个相当完整的答案，代码显示了如何实现它。摘要：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|123273|你可能不想这么做。使用git+describe是一种合理的选择。|ordered-list-item|style|CODE|123274|如果您确实需要这样做，$Id$和$Format$是相当容易的。|123275|任何更高级的东西都需要使用gitattributes和自定义过滤器。我提供了一个$Date$的示例实现。|123276|基于钩子函数的解决方案通常没有帮助，因为它们会使您的工作副本变得肮脏。|123277|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/62264/dealing-with-svn-keyword-expansion-with-git-svn#72874^0|D|7|0|0|B|C|0|B|4|G|8|0|D|D|14|6|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|F|7|10|8|@$A|11|B|12|G|H]]|9|@]|C|$]]|$1|I|3|J|5|F|7|13|8|@$A|14|B|15|G|H]|$A|16|B|17|G|H]]|9|@]|C|$]]|$1|K|3|L|5|F|7|18|8|@$A|19|B|1A|G|H]|$A|1B|B|1C|G|H]]|9|@]|C|$]]|$1|M|3|N|5|6|7|1D|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|1E|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

I wrote up a <a href="https://stackoverflow.com/questions/62264/dealing-with-svn-keyword-expansion-with-git-svn#72874">fairly complete answer</a> to this elsewhere, with code showing how to do it. A summary:

<ol>
<li>You probably don't want to do this. Using <code>git describe</code> is a reasonable alternative.</li>
<li>If you do need to do this, <code>$Id$</code> and <code>$Format$</code> are fairly easy.</li>
<li>Anything more advanced will require using <code>gitattributes</code> and a custom filter. I provide an example implementation of <code>$Date$</code>.</li>
</ol>

Solutions based on hook functions are generally not helpful, because they make your working copy dirty.

blocks|key|123207|text|Git有预提交和后提交挂钩，它们位于每个.git/hooks目录中。只需修改文件和chmod它们，使它们可执行。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|123208|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Git does have pre-commit and post-commit hooks, they are located inside each .git/hooks directory. Just modify the files and chmod them to make them executable.

blocks|key|1122700|text|虽然我已经是一个老掉牙的问答家了，但我想我应该把一个扔进去，因为这已经困扰了我很长时间了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1122701|我习惯于按反向时间顺序列出目录中的文件(有趣吗？)原因是我想看看我最近更改了哪些文件(或者其他人)。|1122702|Git会搞乱我的计划，因为当切换一个分支时，本地回购将完全覆盖(增量)跟踪的文件。我知道.在包装好的本地回购中的副本。|1122703|这样，所有已签出的文件都将带有签出的时间戳，并且不会反映其上次修改的时间……多烦人啊。|1122704|因此，我设计了一个在bash中的一行程序，它将根据IT在文件系统上的内容更新任何文件中的一个属性，根据它在文件系统上的内容来更新它，这样我就可以立即知道最后一次修改的状态，而不必浏览git+log、git+show或任何其他给出指责模式提交时间的工具。|offset|length|style|BOLD|CODE|1122705|下面的过程只在将要提交给回购的跟踪文件中修改$Date：$关键字。它使用git+diff+--name-only，它将列出修改过的文件，而没有其他的.|1122706|在提交代码之前，我将手动使用这个一行代码。不过，有一件事是，在应用此目录之前，我必须导航到回购的根目录。|1122707|下面是Linux的代码变体(粘贴为多行以提高可读性)|1122708|git+diff+--name-only+%7C+xargs+stat+-c+"%25n+%25Y"+2>/dev/null+%7C+\
perl+-pe+'s/[%5E[:ascii:]]//g;'+%7C+while+read+l;+do+\
+++set+--+$l;+f=$1;++shift;+d=$*;+modif=`date+-d+"@$d"`;+\
+++perl+-i.bak+-pe+'s/\$Date:+[\w+\d\/:,.)(%2B-]*\$/\$Date:+'"$modif"'\$/i'+$f;+\
+++git+add+$f;+done|code-block|syntax|javascript|1122709|和OSX|1122710|git+diff+--name-only+%7C+xargs+stat+-f+"%25N+%25Sm"+%7C+while+read+l;+do+\
+++set+--+$l;+f=$1;+shift;+d=$*;+modif=`date+-j+-f+"%25b+%25d+%25T+%25Y"+"$d"`;+\
+++perl+-i.bak+-pe+'s/\$Date:+[\w+\d\/:,.)(%2B-]*\$/\$Date:+'"$modif"'\$/i'+$f;+\
+++git+add+$f;+done|1122711|entityMap^0|0|0|0|0|W|2M|2J|7|2R|8|0|0|23|10|K|0|0|1G|0|0|Q|0|0|0|4|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|16|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|17|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|18|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|19|8|@$J|1A|K|1B|L|M]|$J|1C|K|1D|L|N]|$J|1E|K|1F|L|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1G|8|@$J|1H|K|1I|L|M]|$J|1J|K|1K|L|N]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1L|8|@$J|1M|K|1N|L|M]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1O|8|@$J|1P|K|1Q|L|M]]|9|@]|A|$]]|$1|U|3|V|5|W|7|1R|8|@]|9|@]|A|$X|Y]]|$1|Z|3|10|5|6|7|1S|8|@$J|1T|K|1U|L|M]]|9|@]|A|$]]|$1|11|3|12|5|W|7|1V|8|@]|9|@]|A|$X|Y]]|$1|13|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]]|14|$]]

Although an age-old Q&amp;A. I thought I'd throw one in since this has been bugging me for a long time.

I am used to list the files in a directory by reverse-time order (funny me, heh?). The reason is that I would like to see which files I have (or anyone else has) changed recently.

Git will mess my plans because when switching a branch the local repo will completely overwrite the tracked files from the (incremental... I know...) copies that sit in the packed local repo.

This way all files that were checked out will carry the time stamp of the checkout and will not reflect their last modification time..... How so annoying.

So, I've devised a one-liner in bash that will update a $Date:$ property inside any file WITH THE TIME OF LAST MODIFICATION ACCORDING TO WHAT IT HAS ON FILE SYSTEM such that I will have an immediate status telling of last modification without having to browse the <code>git log</code> , <code>git show</code> or any other tool that gives the commit times in blame mode.

The following procedure will modify the $Date: $ keyword only in tracked files that are going to be committed to the repo. It uses <code>git diff --name-only</code> which will list files that were modified, and nothing else....

I use this one-liner manually before committing the code. One thing though is that I have to navigate to the repo's root directory before applying this.

Here's the code variant for Linux (pasted as a multi-line for readability)

<pre><code>git diff --name-only | xargs stat -c "%n %Y" 2&gt;/dev/null | \
perl -pe 's/[^[:ascii:]]//g;' | while read l; do \
 set -- $l; f=$1; shift; d=$*; modif=`date -d "@$d"`; \
 perl -i.bak -pe 's/\$Date: [\w \d\/:,.)(+-]*\$/\$Date: '"$modif"'\$/i' $f; \
 git add $f; done
</code></pre>

and OSX

<pre><code>git diff --name-only | xargs stat -f "%N %Sm" | while read l; do \
 set -- $l; f=$1; shift; d=$*; modif=`date -j -f "%b %d %T %Y" "$d"`; \
 perl -i.bak -pe 's/\$Date: [\w \d\/:,.)(+-]*\$/\$Date: '"$modif"'\$/i' $f; \
 git add $f; done
</code></pre>

blocks|key|824279|text|也许最常见的SVN属性‘svn:忽略’是通过.gitignore文件而不是通过元数据完成的。恐怕我对其他类型的元数据没有更多的帮助了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|824280|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Perhaps the most common SVN property, 'svn:ignore' is done through the .gitignore file, rather than metadata. I'm afraid I don't have anything more helpful for the other kinds of metadata.

Browsing through the git documentation, I can't see anything analogous to SVN's commit hooks or the "propset" features that can, say, update a version number or copyright notice within a file whenever it is committed to the repository.

Are git users expected to write external scripts for this sort of functionality (which doesn't seem out of the question) or have I just missed something obvious?

Edit : Just to be clear, I'm more interested in, e.g.,

<pre><code>svn propset svn:keywords "Author Date Id Revision" expl3.dtx
</code></pre>

where a string like this:

<pre><code>$Id: expl3.dtx 780 2008-08-30 12:32:34Z morten $
</code></pre>

is kept up-to-date with the relevant info whenever a commit occurs.

Does git have anything like `svn propset svn:keywords` or pre-/post-commit hooks?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

在浏览git文档时，我看不到任何类似于SVN提交钩子或"propset“特性的东西，这些特性可以在提交到存储库时更新文件中的版本号或版权通知。git用户是希望为这种功能编写外部脚本(这似乎并不是不可能的)，还是我忽略了一些显而易见的东西？编辑:为了澄清，我更感兴趣，例如，svn propset svn:keywords "Author Date Id Revision" expl3.dtx像这样的

问git有‘svn propset svn:keywords`’之类的东西吗？
EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问git有‘svn propset svn:keywords`’之类的东西吗？EN

回答 5

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问git有‘svn propset svn:keywords`’之类的东西吗？
EN