You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
that Jonathan Nieder had sent to the mailing list. He suggested using
28
-
the [standard commit-reference format documented in SubmittingPatches](https://github.com/git/git/blob/16a465bc018d09e9d7bbbdc5f40a7fb99c21f8ef/Documentation/SubmittingPatches#L143-L158) in the commit message of the patch.
that Jonathan Nieder had sent to the mailing list. He suggested using
28
+
the [standard commit-reference format documented in SubmittingPatches](https://github.com/git/git/blob/16a465bc018d09e9d7bbbdc5f40a7fb99c21f8ef/Documentation/SubmittingPatches#L143-L158) in the commit message of the patch.
The main difference is that the former starts with an abbreviated
43
-
object id, while the latter starts with an output from `git describe`.
42
+
The main difference is that the former starts with an abbreviated
43
+
object id, while the latter starts with an output from `git describe`.
44
44
45
-
Ævar gave an example of him previously looking for a commit using
46
-
`git log --grep=0386dd37b1` and not finding it because Jonathan had
47
-
not used the standard format.
45
+
Ævar gave an example of him previously looking for a commit using
46
+
`git log --grep=0386dd37b1` and not finding it because Jonathan had
47
+
not used the standard format.
48
48
49
-
Ævar also wondered if "we should have some mode where
50
-
`--grep=<commitish>` will be combined with some mode where we try to
51
-
find various forms of `<commitish>` in commit messages, then normalize
52
-
& match them..."
49
+
Ævar also wondered if "we should have some mode where
50
+
`--grep=<commitish>` will be combined with some mode where we try to
51
+
find various forms of `<commitish>` in commit messages, then normalize
52
+
& match them..."
53
53
54
-
Duy Nguyen replied to that by suggesting we use email style trailers
55
-
like `In-Reply-To: ...` or even `Fixes: ...` to refer
56
-
to related commits, which could make sense as we already use
57
-
[`Signed-off-by: User <email>` trailers](https://github.com/git/git/blob/master/Documentation/SubmittingPatches#L306-L347)
58
-
and some other similar trailers in commit messages.
54
+
Duy Nguyen replied to that by suggesting we use email style trailers
55
+
like `In-Reply-To: ...` or even `Fixes: ...` to refer
56
+
to related commits, which could make sense as we already use
57
+
[`Signed-off-by: User <email>` trailers](https://github.com/git/git/blob/master/Documentation/SubmittingPatches#L306-L347)
58
+
and some other similar trailers in commit messages.
59
59
60
-
SZEDER Gábor also replied to Ævar saying that the `%h (%s, %ad)` is
61
-
even better and more widely used than the standard `%h ("%s", %ad)` as
62
-
the former avoids useless double quotes around the commit title.
60
+
Gábor Szeder also replied to Ævar saying that the `%h (%s, %ad)` is
61
+
even better and more widely used than the standard `%h ("%s", %ad)` as
62
+
the former avoids useless double quotes around the commit title.
63
63
64
-
Jeff King, alias Peff, then commented to Ævar's suggestion about a new
65
-
mode for `--grep=<commitish>`. He gave examples of other tools that
66
-
work better with the standard format:
64
+
Jeff King, alias Peff, then commented to Ævar's suggestion about a new
65
+
mode for `--grep=<commitish>`. He gave examples of other tools that
66
+
work better with the standard format:
67
67
68
-
- web interfaces like GitHub have learned to replace an abbreviated
69
-
object id with a link to a page displaying the object,
68
+
- web interfaces like GitHub have learned to replace an abbreviated
69
+
object id with a link to a page displaying the object,
70
70
71
-
- terminals makes it easy to select object ids, but don't understand
72
-
output from `git describe`.
71
+
- terminals makes it easy to select object ids, but don't understand
72
+
output from `git describe`.
73
73
74
-
Peff acknowledged that the format with an output from `git describe`
75
-
has some benefits:
74
+
Peff acknowledged that the format with an output from `git describe`
75
+
has some benefits:
76
76
77
-
> As far as I can tell, the main advantage of using `v2.11.0-rc3~3^2~1`
78
-
> over its hex id is that it gives a better sense in time of which Git
79
-
> version we're talking about. The date in the parentheses does something
80
-
> similar for wall-clock time, but it's left to the reader to map that to
81
-
> a Git version if they choose.
77
+
> As far as I can tell, the main advantage of using `v2.11.0-rc3~3^2~1`
78
+
> over its hex id is that it gives a better sense in time of which Git
79
+
> version we're talking about. The date in the parentheses does something
80
+
> similar for wall-clock time, but it's left to the reader to map that to
81
+
> a Git version if they choose.
82
82
83
-
But he thought that they were not worth the disadvantages "as in the
84
-
rare instance that I care about the containing version, it's not a big
85
-
deal to use `git tag --contains`".
83
+
But he thought that they were not worth the disadvantages "as in the
84
+
rare instance that I care about the containing version, it's not a big
85
+
deal to use `git tag --contains`".
86
86
87
-
He suggested anyway using something like:
87
+
He suggested anyway using something like:
88
88
89
-
```
90
-
1234abcd (the subject line, 2016-01-01, v2.11.0)
91
-
```
89
+
```
90
+
1234abcd (the subject line, 2016-01-01, v2.11.0)
91
+
```
92
92
93
-
which adds a version after the date, "if we really want to convey that
94
-
information". And he proposed some reasonable rules for this new
95
-
format.
93
+
which adds a version after the date, "if we really want to convey that
94
+
information". And he proposed some reasonable rules for this new
95
+
format.
96
96
97
-
Jonathan replied to Peff's suggestion by discussing the possible
98
-
ambiguities in what the tag name is referring to. This led Jonathan to
99
-
prefer using trailers like `Fixes: ...` as Duy had suggested,
100
-
saying they have been working well for the Linux kernel project.
97
+
Jonathan replied to Peff's suggestion by discussing the possible
98
+
ambiguities in what the tag name is referring to. This led Jonathan to
99
+
prefer using trailers like `Fixes: ...` as Duy had suggested,
100
+
saying they have been working well for the Linux kernel project.
101
101
102
-
In a separate reply to Duy's email, Jonathan copied relevant
103
-
[documentation from the Linux kernel project](https://github.com/torvalds/linux/blob/ae67ee6c5e1d5b6acdb0d51fddde651834096d75/Documentation/process/submitting-patches.rst)
104
-
where they specify a trailer that looks like:
102
+
In a separate reply to Duy's email, Jonathan copied relevant
103
+
[documentation from the Linux kernel project](https://github.com/torvalds/linux/blob/ae67ee6c5e1d5b6acdb0d51fddde651834096d75/Documentation/process/submitting-patches.rst)
* AsciiDoc, the markup language used by [Git's manual and other documentation](https://git-scm.com/docs),
180
179
will get [an official specification under the Eclipse Foundation](https://asciidoctor.org/news/2019/01/07/asciidoc-spec-proposal/).
181
-
182
-
* Google is [seeking open source projects for Google Summer of Code 2019](https://opensource.googleblog.com/2019/01/seeking-projects-for-gsoc-2019.html)
180
+
* Google is [seeking open source projects for Google Summer of Code 2019](https://opensource.googleblog.com/2019/01/seeking-projects-for-gsoc-2019.html).
183
181
The deadline to apply is February 6 at 20:00 UTC, chosen
184
-
organizations will be annouced on February 26.
182
+
organizations will be announced on February 26.
185
183
Git Development Community [is interested](https://public-inbox.org/git/CAP8UFD3Kt3dreMnfAdLiP2yc47kBLoVYCk-2yDw67OkujVY=Ew@mail.gmail.com/T/#m5568b147f03c0b2e9dc96843dc13e85f5b2f187f).
*[New year, new GitHub: Announcing unlimited free private repos and unified Enterprise offering](https://github.blog/2019-01-07-new-year-new-github/) (the former with up to three collaborators per repository)
*[New year, new GitHub: Announcing unlimited free private repos and unified Enterprise offering](https://github.blog/2019-01-07-new-year-new-github/) (the former with up to three collaborators per repository).
189
186
190
187
__Light reading__
191
188
*[A tale of 132 e's](https://linuxwit.ch/blog/2018/12/e98e/) and [the [E]nd of eeeee](https://linuxwit.ch/blog/2018/12/everything-that-lives-is-designed-to-end/) by Iliana Weller, about [e30e/e98e](https://github.com/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee/eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee) GitHub repository and its history
192
189
*[How to teach Git](https://rachelcarmena.github.io/2018/12/12/how-to-teach-git.html) by Rachel M. Carmena
193
190
*[How To Use Git: A Reference Guide](https://dev.to/digitalocean/how-to-use-git-a-reference-guide-6b6) by Lisa Tagliaferri from DigitalOcean
194
191
*[8 Productivity Tips for GitHub](https://dev.to/_darrenburns/8-productivity-tips-for-github-44kn) by Darren Burns
195
-
*[Something Someone Somewhere Uses... Sometimes](https://dev.to/benjaminadk/something-someone-somewhere-uses-sometimes-1kab) by benjaminadk, about [Gitmoji](https://gitmoji.carloscuesta.me/)
192
+
*[Something Someone Somewhere Uses... Sometimes](https://dev.to/benjaminadk/something-someone-somewhere-uses-sometimes-1kab) by benjaminadk, about [gitmoji](https://gitmoji.carloscuesta.me/)
196
193
*[A new free-software forge: sr.ht [LWN.net]](https://lwn.net/Articles/775963/) by Jake Edge; this service was covered in [previous edition of Git Rev News](https://git.github.io/rev_news/2018/12/19/edition-46/#other-news)
197
194
*[Monorepos: Please don’t!](https://medium.com/@mattklein123/monorepos-please-dont-e9a279be011b) by Matt Klein
198
195
-[Monorepo: please do!](https://medium.com/@adamhjk/monorepo-please-do-3657e08a4b70), response by Adam Jacob
@@ -205,14 +202,14 @@ __Light reading__
205
202
[Lerna](https://lernajs.io/) ([Git Rev News: Edition #43](https://git.github.io/rev_news/2018/09/19/edition-43/)) tools for monorepos
206
203
*[Writing Good Commit Messages](https://medium.com/compass-true-north/writing-good-commit-messages-fc33af9d6321) by Ben Hoyt (2018)
207
204
*[Useful Tips for writing better Git commit messages](https://code.likeagirl.io/useful-tips-for-writing-better-git-commit-messages-808770609503) by Egwuenu Gift (2018)
*[How to manage binary blobs with Git](https://opensource.com/life/16/8/how-manage-binary-blobs-git-part-7) by Seth Kenlon (2016)
210
-
*[Migrating Internet Archive to Kubernetes](https://archive.org/~tracey/slides/kubecon/#/) -- slides from presentation at KubeCon 2018; slides [#35](https://archive.org/~tracey/slides/kubecon/#/35) and later are about how Git is used at Archive.org
207
+
*[Migrating Internet Archive to Kubernetes](https://archive.org/~tracey/slides/kubecon/#/) -- slides from presentation at KubeCon 2018; slides [#35](https://archive.org/~tracey/slides/kubecon/#/35) and later are about how Git is used at [archive.org](https://archive.org/)
211
208
212
209
__Git tools and sites__
213
210
214
211
*[OneDev](https://onedev.io) Open source git server with unique features such as language aware code search and navigation, source/diff annotation for code discussion and comprehension, customizable issue field and workflow, write protection for branches/tags/files, etc.
215
-
*[gitmoji | An emoji guide for your commit messages](https://gitmoji.carloscuesta.me/)
212
+
*[gitmoji -- An emoji guide for your commit messages](https://gitmoji.carloscuesta.me/)
0 commit comments