From: Dmitry Gutov <dgutov@yandex.ru>
To: "Alfred M. Szmidt" <ams@gnu.org>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: vc-modify-change-comment for "modern" backend fix
Date: Thu, 19 May 2022 13:24:14 +0300 [thread overview]
Message-ID: <216c8f86-e672-ae48-c43d-37692bc94ec5@yandex.ru> (raw)
In-Reply-To: <E1nrcvk-00059B-0e@fencepost.gnu.org>
On 19.05.2022 12:58, Alfred M. Szmidt wrote:
> Okay, but how will this work in fossil? Similar to editing a single
> commit during a rebase?
>
> Fossil has no concept of rebase. Amending makes a new commit, and the
> last commit message is shown when viewing the timeline/log.
>
> ~/tt $ fossil timeline -R foo.fossil
> === 2022-05-17 ===
> 09:42:27 [3b410767c6] Edit [73bf888ab97bd2c3|73bf888ab9]: Edit check-in comment. (user: ams)
> 07:50:06 [30aa7e8b06] Edit [73bf888ab97bd2c3|73bf888ab9]: Edit check-in comment. (user: ams)
> 07:33:59 [1c13590b96] Edit [73bf888ab97bd2c3|73bf888ab9]: Edit check-in comment. (user: ams)
> 07:30:34 [73bf888ab9] zork zork zborkrkrk (user: ams tags: trunk)
> 07:30:02 [40289e9363] initial empty check-in (user: ams tags: trunk)
> +++ no more data (5) +++
> ~/tt $ fossil amend -m "this is a new message" 40289e9363 -R foo.fossil
> hash: 40289e9363e0e3e1fe5e2df9c9827fe65e51f547 2022-05-17 07:30:02 UTC
> tags: trunk
> comment: this is a new message (user: ams)
> ~/tt $ fossil timeline -R foo.fossil
> === 2022-05-19 ===
> 09:56:34 [5a950dc2f6] Edit [40289e9363e0e3e1|40289e9363]: Edit check-in comment. (user: ams)
> === 2022-05-17 ===
> 09:42:27 [3b410767c6] Edit [73bf888ab97bd2c3|73bf888ab9]: Edit check-in comment. (user: ams)
> 07:50:06 [30aa7e8b06] Edit [73bf888ab97bd2c3|73bf888ab9]: Edit check-in comment. (user: ams)
> 07:33:59 [1c13590b96] Edit [73bf888ab97bd2c3|73bf888ab9]: Edit check-in comment. (user: ams)
> 07:30:34 [73bf888ab9] zork zork zborkrkrk (user: ams tags: trunk)
> 07:30:02 [40289e9363] this is a new message (user: ams tags: trunk)
So it's like the commit log is part of the content tree, edited by the
last commit. Cool.
prev parent reply other threads:[~2022-05-19 10:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 7:04 vc-modify-change-comment for "modern" backend fix Alfred M. Szmidt
2022-05-17 8:36 ` Alfred M. Szmidt
2022-05-17 12:02 ` Eli Zaretskii
2022-05-17 18:31 ` Stefan Monnier
2022-05-17 19:10 ` Alfred M. Szmidt
2022-05-17 23:20 ` Dmitry Gutov
2022-05-18 6:34 ` Alfred M. Szmidt
2022-05-18 11:29 ` Eli Zaretskii
2022-05-19 6:11 ` Alfred M. Szmidt
2022-05-19 14:47 ` Stefan Monnier
2022-05-19 0:05 ` Dmitry Gutov
2022-05-19 6:11 ` Alfred M. Szmidt
2022-05-19 9:25 ` Dmitry Gutov
2022-05-19 9:58 ` Alfred M. Szmidt
2022-05-19 10:24 ` Dmitry Gutov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=216c8f86-e672-ae48-c43d-37692bc94ec5@yandex.ru \
--to=dgutov@yandex.ru \
--cc=ams@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).