git-pr

fix: use eventlog time for pr details rss

created pr with 8.1 on 2024-07-20T15:02:56Z · by 6baffbe4

pr_reviewed on 2024-07-21T15:50:45Z · by c8ef7d19

cmds

checkout latest patchset:

ssh pr.pico.sh print 8 | git am -3

checkout any patchset in a patch request:

ssh pr.pico.sh print 8.[rev] | git am -3

add changes to patch request:

git format-patch main --stdout | ssh pr.pico.sh pr add 8

Patchset `8.1` on 2024-07-20T15:02:56Z · commit 3ba22c2

→ docs: fix typo / minor rewording in readme

Jeremy Clarke 2024-07-20T14:59:21Z

docs: fix typo / minor rewording in readme

Jeremy Clarke 2024-07-20T14:59:21Z

Semantic diff summary

0 added, 0 modified, 0 signature changed, 0 removed across 0 analyzed files (1 file skipped: unsupported file type)

+5 -5 README.md #

......@@ -124,11 +124,11 @@ git push origin main
# Done!
```

The fundamental collaboration tool here is `format-patch`. Whether you a
submitting code changes or you are reviewing code changes, it all happens in
code. Both contributor and owner are simply creating new commits and generating
patches on top of each other. This obviates the need to have a web viewer where
the reviewer can "comment" on a line of code block. There's no need, apply the
The fundamental collaboration tool here is `format-patch`. Whether you are
submitting code changes or reviewing them, it all happens in code. Both
contributor and owner are simply creating new commits and generating patches
on top of each other. This obviates the need to have a web viewer where the
reviewer can "comment" on a line of code block. There's no need, apply the
contributor's patches, write comments or code changes, generate a new patch,
send the patch to the git server as a "review." This flow also works the exact
same if two users are collaborating on a set of changes.

...	...		@@ -124,11 +124,11 @@ git push origin main
124	124		# Done!
125	125		```
126	126
127		-	The fundamental collaboration tool here is `format-patch`. Whether you a
128		-	submitting code changes or you are reviewing code changes, it all happens in
129		-	code. Both contributor and owner are simply creating new commits and generating
130		-	patches on top of each other. This obviates the need to have a web viewer where
131		-	the reviewer can "comment" on a line of code block. There's no need, apply the
	127	+	The fundamental collaboration tool here is `format-patch`. Whether you are
	128	+	submitting code changes or reviewing them, it all happens in code. Both
	129	+	contributor and owner are simply creating new commits and generating patches
	130	+	on top of each other. This obviates the need to have a web viewer where the
	131	+	reviewer can "comment" on a line of code block. There's no need, apply the
132	132		contributor's patches, write comments or code changes, generate a new patch,
133	133		send the patch to the git server as a "review." This flow also works the exact
134	134		same if two users are collaborating on a set of changes.

git-pr

Patchset 8.1 on 2024-07-20T15:02:56Z · commit 3ba22c2

Patchset `8.1` on 2024-07-20T15:02:56Z · commit 3ba22c2