On Thursday, July 21, 2022 at 4:07:37 PM UTC+3 philip...@iee.email wrote: [...]
> > FWIW, a recent discussion on the main Git list [1] brought to my > attention > > that there exist support for setting textual branch descriptions: a > config > > setting branch.<name>.description, which can be manipulated with the > > `git branch --edit-description` command. See the gitconfig manual page > for > > more details. > > > > 1. https://public-inbox.org/git/xmqqilnr1hff.fsf@gitster.g/ > > That discussion is looking interesting. > > However the discussion about Commit-IDs at > https://lore.kernel.org/git/bdbe9b7c1123f70c0b4325d...@that.guru/ > <https://lore.kernel.org/git/bdbe9b7c1123f70c0b4325d778af1df8fea2bb1b.ca...@that.guru/> > > should also be looked at to see some of the nuances that need to be > considered (e.g. https://lore.kernel.org/git/yth9tcce...@mit.edu/ > <https://lore.kernel.org/git/yth9tccexfmag...@mit.edu/>). > > I'm for the idea that it should be possible for branch descriptions to > be portable and be passed between repos and devs, but ultimately it is > for the local dev to decide which description to accept, use and publish. > Yes, Git already has similar mechanism in the form of Git notes which allows attaching messages to individual commits - basically, it even supports merging of notes. I mean, as soon as we push any "metainformation" feature to be distributed, the complexity of implementing it skyrockets quite fast. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/15778a7b-3787-4b98-a5cc-e9beecc11f65n%40googlegroups.com.
