Update patch set 2

Browse Source

Patch Set 2:

The anticipated workflow was something like this...

If you're going to create a new presentation, perhaps with a different scope or topic, you can request a branch be created (usually from the template branch, but optionally from one of the other existing presentation). If you have updates for a presentation on an existing branch, just submit them against that branch. If you present one, note the commit+branch or the change in review which you presented and request a tag corresponding with it. Updating existing presentations is fine since it allows people to collaborate on keeping them up to date and not having to duplicate work. Going back and revising the tagged state of a presentation given at a particular event makes less sense, as it would be saying that what was presented wasn't what was presented.

Patch-set: 2

...

This commit is contained in:

Gerrit User 5263 2019-10-25 13:45:15 +00:00 committed by Gerrit Code Review

parent 1cc9a1b110

commit 0db6bc344d

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Show Stats Download Patch File Download Diff File Expand all files Collapse all files

Diff Content Not Available