enhancement: command to change the log message of a revision after the fact

[GoogleCodeExporter]

Being able to add or change the log message of a revision after the fact would 
be great.

Ditto to being able to change the name of a session. I realize there is a write 
once design philosophy to the repo, but perhaps these could be applied as a new 
session/patch definition that applies to the session chain. So when reading in 
the sessions in a given chain, boar could see that revision # had a log message 
added to it, or session example is now called work_example.

Since the only way to filter/sort sessions is by overloading the session name 
and using tools like grep/sort, being able to change session names after the 
fact is very useful since some of these usability factors aren't immediately 
obvious and someone might not have settled on naming conventions for sessions 
that work well for them until after using boar awhile and then finding they are 
stuck with their initial poorly thought out session names.

/cb

Original issue reported on code.google.com by cryptob...@gmail.com on 1 Mar 2012 at 11:28

[GoogleCodeExporter]

the suggestion to implement session renaming as a session that masks previous 
session names was due to the fact that the session.json file stores the session 
name thus changing the session name would involve changing that value for all 
the session.json files, and then rehashing and updating the session.md5 file. 
An alternative would be if sessions were internally stored as a guid of some 
kind, and the guid to "human readable" session names were stored in a single 
file. This would make session renaming trivial, and the integrity of the boar 
repo would be totally unaffected since the session name is ultimately for the 
benefit of the end user to be able to have a "friendly name" that has some 
meaning to them, and to make the output of the list command likewise 
meaningful. Given that human readable session names are for the benefit of the 
user, if sessions were implemented as guids on the backend, then the friendly 
name aliases that boar presents to the user are that much friendlier by virtue 
of the fact that user can easily rename them without boar having to touch the 
sessions folder at all. There can be a single sessions.json folder somewhere 
that maintains these mappings, and if you're being very paranoid this file can 
be version controlled or datestamped and backed up so a user can easily restore 
an older version should something go amiss.

/cb

/cb

Original comment by cryptob...@gmail.com on 1 Mar 2012 at 1:08

[GoogleCodeExporter]

sessions.json file*

Original comment by cryptob...@gmail.com on 1 Mar 2012 at 1:11

[GoogleCodeExporter]

I actually think that one of the features of log messages is the fact that they 
can't be changed... A permanent record of why the commit was made, or lack 
thereof. If a user needs an editable change log for what is going on in a tree, 
there is always the option of using a "changelog.txt" file and simply version 
it as any other file.

Renaming sessions would be useful, but that is another thing (one suggestion 
per issue please, if possible).

Original comment by ekb...@gmail.com on 2 Mar 2012 at 5:15

• Changed state: WontFix