Re: Best practices/conventions for tags and references in commit message

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Search the mailing list archives for git-interpret-trailers. It's coming. :)


...Johan

On Tue, May 27, 2014 at 1:26 PM, Thomas Koch <thomas@xxxxxxx> wrote:
> Hi,
>
> different projects or tools have conventions to include machine parsable
> information in commit messages, e.g.:
>
> Closes: #42
> Thanks: my mother, my wife
> Git-Dch: Ignore
> Commit-Id: 50M3R34LLYR4ND0MB1TSANDNUMB3R5
>
> (see thread: "RFE: support change-id generation natively" for Commit-Id)
> ("Git-Dch: Ignore" ecludes the commit from the changelog)
>
> Are you aware of any convention or best practices for such tags that are used
> in more than one project? Are there more tags like these?
>
> Maybe it would also be helpful to have some more plumbing support from Git for
> such tags. But I've not yet thought enough about this.
>
> Best regards, Thomas Koch
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
Johan Herland, <johan@xxxxxxxxxxx>
www.herland.net
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]